From tk at tkinnovations.net  Thu Mar  1 08:19:19 2012
From: tk at tkinnovations.net (tk at tkinnovations.net)
Date: Thu, 01 Mar 2012 01:19:19 -0700
Subject: [wxruby-development] locked wiki
Message-ID: <20120301011919.14855tnfll5pqpl3@host318.hostmonster.com>

Looks like it has been locked. I went to restore the vandalized parts  
and had a write error. I sent an email to the tom at ... contact per the  
error message thanking and asking for write privilages please.

I'd also like to contribute a short tutorial for Wx::CollapsiblePane.


TK



From noreply at rubyforge.org  Tue Mar 13 15:11:29 2012
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 13 Mar 2012 15:11:29 +0000 (UTC)
Subject: [wxruby-development] [ wxruby-Bugs-29542 ] [BUG] object allocation
	during garbage collection phase
Message-ID: <20120313151129.D1D33263026@rubyforge.org>

Bugs item #29542, was opened at 2012-03-13 16:11
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=29542&group_id=35

Category: Incorrect behavior
Group: current
Status: Open
Resolution: None
Priority: 3
Submitted By: Ad Machielsen (admachielsen)
Assigned to: Nobody (None)
Summary: [BUG] object allocation during garbage collection phase 

Initial Comment:
If in the examples/minimal/nothing.rb script the line:
GC.stress = true
is added, a stack dump (see below) occurs directly after closing the frame.

If the GC is disabled before closing Frame:
-add event handler to (sub-classed Frame):
 evt_close :on_close
-and
 def on_close(event)
   GC.disable
   event.skip
 end
The stackdump doesn't occur.

Note: In the function Wx::App.gc_stress there is a line <GC.stress>, this should be <GC.stress = true>, I think!

Test environment
================
- Windows 7
- ruby 1.9.3p125 (Ruby installer)
- wxruby-ruby19-2.0.1-x86-mingw32.gem

stackdump
=========
C:/Ruby193/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86-mingw32/lib/wx/classes/app.rb:16: 
[BUG] object allocation during garbage collection phase
ruby 1.9.3p125 (2012-02-16) [i386-mingw32]

-- Control frame information -----------------------------------------------
c:0006 p:---- s:0017 b:0017 l:000016 d:000016 CFUNC  :on_run
c:0005 p:---- s:0015 b:0015 l:000014 d:000014 CFUNC  :main_loop
c:0004 p:0053 s:0012 b:0012 l:000011 d:000011 METHOD C:/Ruby193/lib/ruby/gems/1.9.1/gems/
wxruby-ruby19-2.0.1-x86-mingw32/lib/wx/classes/app.rb:16
c:0003 p:0047 s:0006 b:0006 l:001d4c d:00152c EVAL   C:/Ruby193/servers/nothing.rb:20
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
c:0001 p:0000 s:0002 b:0002 l:001d4c d:001d4c TOP
-- Ruby level backtrace information ----------------------------------------
C:/Ruby193/servers/nothing.rb:20:in `<main>'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86-mingw32/lib/wx/classes/app.rb:16:in `run'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86-mingw32/lib/wx/classes/app.rb:16:in `main_loop'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/wxruby-ruby19-2.0.1-x86-mingw32/lib/wx/classes/app.rb:16:in `on_run'


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=29542&group_id=35