therubyracer gem crashes interpreter #1771

Closed
sickill opened this Issue Jun 5, 2012 · 6 comments

Projects

None yet

2 participants

@sickill
sickill commented Jun 5, 2012

I'm trying to run ascii.io on rubinius 2.0 and I encountered following error while trying to run rails server (same error when I try rails console): https://gist.github.com/2877925

@brixen
Member
brixen commented Jun 5, 2012

You are using therubyracer, which has known and very severe issues with memory management that typically manifest like that backtrace. I'm not positive it is the issue, but could you try reducing the dependencies and see if you still have the issue?

@sickill
sickill commented Jun 5, 2012

I have just disabled "twitter-bootstrap-rails" gem and it boots correctly. From the look of Gemfile.lock it seems it requires rubyracer like you said. So what are the options?

@brixen
Member
brixen commented Jun 6, 2012

There is currently work being done on therubyracer to address the memory issues. Sorry, there is not a simple workaround yet. You can track the issue on therubyracer list from the link here #1683.

@sickill
sickill commented Jun 6, 2012

No worries. I'm not in a hurry. I'm just playing with rubinius and thought I'll report an issue. I'll watch rubyracer one then. Thx!

@sickill
sickill commented Jun 6, 2012

Should we close this one or keep it opened for future?

@brixen
Member
brixen commented Jun 6, 2012

Since it's not something Rubinius can fix, I'll close it. The issue with therubyracer can be found from searching tickets here.

@brixen brixen closed this Jun 6, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment