Greetings,
While slowly moving SWT/Fox (swtfox.sf.net) to 3.0
compatibility, I eventually got stuck with this error.
Here's how it happens:
- Eclipse 3.0 M5 or later required (may happen with earlier
milestones too - not sure; does NOT happen with Eclipse 2.X)
- This message appears, but only _sometimes_, when
Eclipse+SWT/Fox is started - jst after the main window is mapped. Then the
window is not painted at all, but the CPU consumption is low.
- This happens more frequently when Eclipse+SWT/Fox
is started for debugging.
- All other threads seem to sleep or wait on
locks..
From what I've heard, these types of messages are reported by
Xlib when x11 package corruption happens, as a result of calling Xlib from
one thread, while another is already inside XLib.
This may happen if SWT is called from the wrong thread
(but there are guards in all SWT methods against this) or if a Unix signal
handler calls into XLib. Neither of these seems probable to me. _However_ there
may be some race condition involved after all, because every time this happens,
I see the small orange progressbar of a background task drawn..
So any insignt on what the problem+fix was for the similar
23472 bug in Eclipse 2+SWT/GTK whould be greatly appreciated - it may
help me chasing the issue. Christophe has reported in the comments of the
bug that it is fixed since build 20030206, but without any
additional details.
Yes, I know the bug I'm referring to is fixed almost one year
ago. Still, anyone?
Thanks,
Ivan
|