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.

Sign up for GitHub

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

Jump to bottom

Workarounds for jRuby support? #44

Open
digitalextremist opened this issue Jun 26, 2015 · 1 comment
Open

Workarounds for jRuby support? #44

digitalextremist opened this issue Jun 26, 2015 · 1 comment

Comments

@digitalextremist
Copy link

It seems all extension code is in C, for MRI/Rubinius. Are there any known ways to work around this, short of implementing Java bindings by some means?
@TheKidCoder
Copy link

One recommendation that I have done is the past is to just use the JVM tooling for profiling. First hand experience will tell you that finding memory leaks with VisualVM is quite nice. Here is some more info: http://blog.headius.com/2010/07/browsing-memory-jruby-way.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@digitalextremist @TheKidCoder