Community
Participate
Working Groups
with some searches, expanding all results in "serach" view makes eclipse crash. ./eclipse -clean The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 124328 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.) Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0xb74aa767] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb74aa81e] #2 /usr/lib/libX11.so.6 [0xb773ade9] #3 /usr/lib/libX11.so.6(XFreeCursor+0x25) [0xb7715cb5] #4 /usr/lib/libqt-mt.so.3(_ZN11QCursorDataD1Ev+0xbc) [0xb6b4bbec] #5 /usr/lib/libqt-mt.so.3(_ZN7QCursorD1Ev+0x40) [0xb6b4bd40] #6 /usr/lib/libqt-mt.so.3 [0xb6b4bd8b] #7 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7dc2b29] #8 /usr/lib/libgdk-x11-2.0.so.0 [0xb79326c8] #9 /usr/lib/libX11.so.6(_XError+0xd9) [0xb77337d9] #10 /usr/lib/libX11.so.6 [0xb773b798] #11 /usr/lib/libX11.so.6(_XReply+0x15a) [0xb773bb4a] #12 /usr/lib/libX11.so.6(XGetGeometry+0x6d) [0xb771783d] #13 /usr/lib/libgdk-x11-2.0.so.0(gdk_pixmap_foreign_new_for_display+0xba) [0xb793353a] #14 /usr/lib/libgdk-x11-2.0.so.0(gdk_pixmap_foreign_new+0x1a) [0xb793359a] #15 /usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so(drawListViewItem+0x14c) [0xb70a9eac] #16 /usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so [0xb70befce] #17 /usr/lib/libgtk-x11-2.0.so.0(gtk_paint_flat_box+0xf9) [0xb72e5199] #18 /usr/lib/libgtk-x11-2.0.so.0 [0xb737e1a1] #19 /usr/lib/libgtk-x11-2.0.so.0 [0xb737f5b2] i fiddled with the xorg-driver (fglrx vs radeonhd) and downgraded the only x-raletd package being update the last days (down to xserver-xorg-core_1.4.2-10_i386.deb). but to no avail. thus i suspect an swt bug. system is debian/unstable x86 X.org 1.4.2 eclipse/gtk, Version: 3.4.1 Build id: M20080911-1700
How did you install Eclipse? What VM are you using (please provide Help > About > Configuration Details)? Do you have any hs_err_pid log files lying around? Check in your eclipse/ folder.
> How did you install Eclipse? got archive, unpacked to /opt/eclipse, done. > What VM are you using (please provide Help > About > Configuration Details)? see attachment > Do you have any hs_err_pid log files lying around? > Check in your eclipse/ folder. neither in installation folder nor workspace nor ~/.eclipse/
Created attachment 126845 [details] output of Help > About > Configuration Details
Notice libqt-mt in the stacktrace, try not using KDE or not using a GTK theme that uses the qt drawing engine.
> Notice libqt-mt in the stacktrace, try not using KDE or not using a GTK theme > that uses the qt drawing engine. sorry, can't follow you. - i use kde as de, so i'd like to have my apps as much as possible to blend in - the qt engine has never been an issue before -- and i use it for years now while switching engine might be workaround, i don't see how that would solve the issue at hand -- unless it is in fact effected by a bug in the engine (but nothing related to either qt or gtk themes has been updated the last few weeks).
In the past, the qt engine had some bad bugs. It should be easy enough for you switch to some other theme engine to help us determine if this problem only happens with the qt-engine. Can you reproduce the bug at will (using a set of steps) ?
> It should be easy enough for you switch to some other theme engine to help us > determine if this problem only happens with the qt-engine. oh, misunderstanding. i understood you were proposing to simply switch away. well, i tried several gtk engine themes and, indeed, the crash is not reproducibly. the moment is witch back to the qt/kde theme it dies again. so, it really seems to be a problem with the qt engine. any hints what to mention when i file a bug report with debian?
(In reply to comment #7) > so, it really seems to be a problem with the qt engine. any hints what to > mention when i file a bug report with debian? Not really, the stack in post in the initial comment. Sorry.
