Re: Fwd: Re: [Fxruby-users] random crashes with FXTable

[Lyle J. <jl...@cf...>]

Emmanuel Touzery wrote:

>     This bug really blocks me, as the application is not usable in this
> state; I was wondering if you could just tell me approximately when you hope
> to fix it (days, weeks, months?).

I am still trying to find a way to *consistently* reproduce the crash 
under Linux. Unlike your experience, the program doesn't crash when I 
simply try to load the glossary file (lyle-good.glo). I did get it to 
crash once, I think in the Bibliography dialog box, but haven't been 
able to do that again.

>     I tried with ruby 1.8 and the problems persist. I tried to fix it
> myself, but it seems to be some kind of memory corruption problem, and
> without knowledge of the source, i'm not getting anywhere. I would try to
> reduce the source code related to the bug, but it's so easy to reproduce,
> and the code is generally so simple, that i guess it wouldn't help (only
> maybe if i reduce it a lot and try to port it to FOX/C++ to see if it's a
> FOX bug maybe.. but it would take me forever...).

As already noted, it's not so easy to reproduce (for me anyways ;) I 
agree with you that it's probably some kind of memory corruption 
problem; most of these difficult-to-reproduce bugs end up being related 
to interactions with Ruby's garbage collector. As a workaround, you 
might simply try disabling garbage collection altogether by adding the line:

     GC.disable

at the beginning of the program.