fxruby users - Jan 2007 - "This FXTextField * already released" error..

Hi,

I have a strange bug that comes up now and then, and for which I cannot
find code that reproduces it, unfortunately. It happens once, the
application crashes, I do exactly the same, and this time it works.

The message is: "This FXTextField * already release".

Does anyone have an idea where it could come from? I never release
anything under FXRuby, since Ruby is supposed to take care of that, so
I''m not sure where to track that problem... Full message is here:

---------------
This FXTextField * already
releasedc:/ruby/lib/ruby/site_ruby/1.8/fox16/aliases.rb:4789:in
`setText''c:/ruby/lib/ruby/site_ruby/1.8/fox16/aliases.rb:4789:in
`text=''./lib/gui/widget/db_text_field.rb:13:in
`val=''./lib/gui/editor/db_fk_editor.rb:93:in
`chooseLookup''./lib/gui/editor/db_fk_editor.rb:39:in
`initialize''c:/ruby/lib/ruby/site_ruby/1.8/fox16/responder2.rb:57:in
`call''c:/ruby/lib/ruby/site_ruby/1.8/fox16/responder2.rb:57:in
`onHandleMsg''./db_fk_fields.rb:5:in
`execute''./db_fk_fields.rb:5:in
`showEditor''./lib/gui/widget/db_fk_field.rb:64:in
`onKeyPress''c:/ruby/lib/ruby/site_ruby/1.8/fox16/responder2.rb:57:in
`call''c:/ruby/lib/ruby/site_ruby/1.8/fox16/responder2.rb:57:in
`onHandleMsg''my_app.rb:127:in `run''my_app.rb:127
---------------

Thanks for your ideas!

Philippe Lang

On Jan 19, 2007, at 7:56 AM, Philippe Lang wrote:
> I have a strange bug that comes up now and then, and for which I  
> cannot
> find code that reproduces it, unfortunately. It happens once, the
> application crashes, I do exactly the same, and this time it works.
>
> The message is: "This FXTextField * already release".
>
> Does anyone have an idea where it could come from?
That message indicates that the underlying C++ object (in this case,  
an FXTextField) that a Ruby object is pointing to has already been  
deleted (freed). It''s not something that you should see under normal  
circumstances, and it may indicate a bug in FXRuby''s GC code  
(especially since you report that the behavior is inconsistent).

If it''s something you''d like for me to take a look at, please
send me
the code off-line.

Thanks,

Lyle