-
Notifications
You must be signed in to change notification settings - Fork 17
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
GC Operation on Unregistered Thread #12
Comments
Note that James continues to /run/, I just keep seeing this error and am wondering what's going on. |
Hi Devin! Thanks for the well described issue. I am afraid that I can't tell you much more than that I've filed a ticket with MacRuby: https://www.macruby.org/trac/ticket/1421 You'll find more information regarding this there. (Including a link back to this) In short: It is benign, but of course nothing nice to look at. Cheers, |
Hey Florian, Thanks for filing an issue on my behalf. I had the sneaking suspicion this issue would be closed out of hand as a problem with MacRuby and not with Regards, |
Hey Devin, I'll leave it open for now – the point you mention is a good one. Cheers, |
I'm seeing a similar issue, with a little more information that could be helpful. James seems to work fine aside from the warning. macruby(93824,0x107481000) malloc: *** auto malloc[93824]: error: GC operation on unregistered thread. Thread registered implicitly. Break on auto_zone_thread_registration_error() to debug. |
Hi @daveshenk! Thanks a lot for reporting. It seems, MacRuby closed this as "wontfix" as the problem seems to be in an OSX framework, see https://www.macruby.org/trac/ticket/1375. |
James seems to work, but I am getting a macruby 0.10 GC error. I installed using rvm version 1.9.2.
Here's the script I'm running via
james time_dialog.rb
`~> james time_dialog.rb
James: Using dialogs in time_dialog.rb for our conversation, Sir.
Possibilities:
Possibilities:
macruby(66211,0x105799000) malloc: *** auto malloc[66211]: error: GC operation on unregistered thread. Thread registered implicitly. Break on auto_zone_thread_registration_error() to debug.
Possibilities:
...`
The text was updated successfully, but these errors were encountered: