I’ve been fighting this issue for some time now, and I’ve been reading
all of the recent posts regarding how Ruby’s threading model can fight
with other “real” threads due to stack corruption.
However, I see random crashes when I’m using embedded browsers (gecko or
webkit) in my application. I’m guessing that it has to do with the fact
that my callbacks might be triggered while some of the browser’s own
threads are still operating (I’m not doing anything tricky, just
handling nearly every signal).
I’ve been meaning to try and dig into this issue a bit more to see if I
can come up with a better threading solution, but I haven’t gotten the
time. However, it’s extremely annoying, and it is certainly something
that would keep this application from being ready for prime time.
Has anyone else observed this behavior and/or does anyone have any
suggestions as to how to try and keep it from happening?
excalibur$ ruby -v
ruby 1.8.6 (2007-09-24 patchlevel 111) [x86_64-linux]
I’m using a relatively recent WebKit build (from a couple of weeks ago),
and the versions of the gecko development libs current with Ubuntu 8.0.4
with ruby-gnome2 that’s been built from source.
Thanks in advance for any ideas or info.