[ruby-core:48624] [ruby-trunk - Bug #7059][Third Party's Issue] rb_name_err_mesg_new at shut down appears to cause: [BUG] object allocation during garbage collection phase

Issue #7059 has been updated by mame (Yusuke Endoh).

Status changed from Open to Third Party's Issue
Priority changed from High to Normal

harrison.uhl (Harrison Uhl) wrote:
> Having read about a "object allocation during garbage collection" issue in WxRuby,

Could you give me a pointer?


> WHILE it does appear that there might be a bug in WxRuby initiating the crash,  IT appears that msvcrt-ruby is also trying to instantiate a new object (during Garbage Collection)

What made you thought so?
I don't know wxRuby's architecture, but the backtrace suggests that wxRuby
attempted to create an object from a thread not managed by Ruby core.

So, could you please contact wxRuby team first?

-- 
Yusuke Endoh <[e-mail]>
----------------------------------------
Bug #7059: rb_name_err_mesg_new at shut down appears to cause: [BUG] object allocation during garbage collection phase
https://bugs.ruby-lang.org/issues/7059#change-32039

Author: harrison.uhl (Harrison Uhl)
Status: Third Party's Issue
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: 1.9.3p194


On shut down of a long running app, a rb_name_err_mesg_new appears to be causing a "object allocation during garbage collection"

It pops up a Windows 7 crash window which says the error is in msvcrt-ruby.dll

I'm using WxRuby to create a GUI app, and OCRA to create the exe.  The app is just a small test app, and does what it is suppose to.

Having read about a "object allocation during garbage collection" issue in WxRuby, I wrapped the WxRuby dispatch() method with a GC.disable; oldDispatch; GC.enable

Attached are two crash dumps, one before wrapping dispatch() and one after.

After wrapping dispatch(), I started and shut down the app about a dozen times.  In all cases it terminated normally.

In both cases that generated the crashes, I'd left the app running overnight.  (The app was doing nothing except waiting in its idle loop.)


WHILE it does appear that there might be a bug in WxRuby initiating the crash,  IT appears that msvcrt-ruby is also trying to instantiate a new object (during Garbage Collection)

ALSO: Why is the rb_name_err_mesg_new not handled more gracefully, say with an informative Ruby exception (perhaps giving the missing name.)

Because of these reasons, I listed this as a Ruby error in the hopes that a patch to msvcrt-ruby will make the nature of the (possible) WxRuby error much clearer.

Please don't bump this to WxRuby without explaining the above apparent msvcrt-ruby issues.

Thanks
Harrison
 


-- 
http://bugs.ruby-lang.org/