wxruby development - Nov 2007 - [ wxruby-Bugs-15666 ] bigdemo crashes after using the arrow keys to select the widgets

Bugs item #15666, was opened at 2007-11-15 21:28
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=15666&group_id=35

Category: Incorrect behavior
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Brian Takita (btakita)
Assigned to: Nobody (None)
Summary: bigdemo crashes after using the arrow keys to select the widgets

Initial Comment:
(wxruby:7774): Gtk-CRITICAL **: gtk_window_realize_icon: assertion
`info->icon_pixmap == NULL'' failed
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxArtProvider.rbw:22:
warning: already initialized constant ArtClients
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxArtProvider.rbw:72:
warning: already initialized constant ArtIDs
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxArtProvider.rbw:22:
warning: already initialized constant ArtClients
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxArtProvider.rbw:72:
warning: already initialized constant ArtIDs
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/ShapedWindow.rbw:17:
warning: already initialized constant BUTTON_CLOSE
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxCursor.rbw:47:
warning: already initialized constant Cursors
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxArtProvider.rbw:22:
warning: already initialized constant ArtClients
/usr/local/lib/ruby/gems/1.8/gems/wxruby-1.9.2-i686-linux/samples/bigdemo/wxArtProvider.rbw:72:
warning: already initialized constant ArtIDs

The program ''wxruby'' received an X Window System error.
This probably reflects a bug in the program.
The error was ''BadAlloc (insufficient resources for
operation)''.
  (Details: serial 13719 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


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

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