Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AIOOBE in ThreadContext#postYield #1982

Closed
nirvdrum opened this issue Sep 17, 2014 · 2 comments
Closed

AIOOBE in ThreadContext#postYield #1982

nirvdrum opened this issue Sep 17, 2014 · 2 comments

Comments

@nirvdrum
Copy link
Contributor

@nirvdrum nirvdrum commented Sep 17, 2014

Since the fix from @subbuss for #1980 went in, I'm now getting getting an AIOOBE that I wasn't before. I'm not sure what the cause is, but it appears when rspec has completed running all the specs in one file and then begins its cleanup.

ThreadContext.java:288:in `popScope': java.lang.ArrayIndexOutOfBoundsException: -7
    from ThreadContext.java:990:in `postYield'
    from InterpretedIRBlockBody.java:54:in `commonYieldPath'
    from IRBlockBody.java:66:in `call'
    from Block.java:106:in `call'
    from RubyProc.java:294:in `call'
    from RubyProc.java:220:in `call'
    from Ruby.java:3178:in `tearDown'
    from Ruby.java:3162:in `tearDown'
    from Main.java:303:in `internalRun'
    from Main.java:226:in `run'
    from Main.java:199:in `main'
$ ruby -v
jruby 9000.dev-SNAPSHOT (2.1.2p142) 2014-09-17 394befd Java HotSpot(TM) 64-Bit Server VM 25.20-b23 on 1.8.0_20-b26 [linux-amd64]
@headius
Copy link
Member

@headius headius commented Sep 17, 2014

@nirvdrum
Copy link
Contributor Author

@nirvdrum nirvdrum commented Jan 15, 2015

I'm pretty sure this was fixed somewhere along the way. I'll re-open if I find otherwise.

@nirvdrum nirvdrum closed this Jan 15, 2015
@enebo enebo added this to the 9.0.0.0.pre2 milestone Jan 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants