Community
Participate
Working Groups
Created attachment 268762 [details] Selecting Find/Replace history -> crash Find/replace: Selecting find history leads to some kind of crash. No further interaction with X possible. (see attachement). Killing eclipse on tty 2 is possible. Version: Oxygen (4.7) Build id: I20170524-2000 (update 06/06/2017) System (uname -a) Linux dhcp1100.se.dfs.de 4.11.3-200.fc25.x86_64 #1 SMP Thu May 25 19:03:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Most current Fedora 25 (update 06/06/2017)
Created attachment 268763 [details] Selecting Find/Replace history
Please atttach jstack dump.
Created attachment 268764 [details] output from 'jstack -l PID'
(In reply to Sven Rathgeber from comment #3) > Created attachment 268764 [details] > output from 'jstack -l PID' Thanks, stack shows idling UI. So you can't do anything, neither in the dialog nor in the editor? Moving to SWT.
> So you can't do anything, neither in the dialog nor in the editor? Thanks for replying so quickly. That's right. Can not do anything with X. Neither eclipse, nor any other UI functionality.
(In reply to Sven Rathgeber from comment #0) > Created attachment 268762 [details] > Selecting Find/Replace history -> crash > > Find/replace: Selecting find history leads to some kind of crash. > No further interaction with X possible. (see attachement). > Killing eclipse on tty 2 is possible. > > Version: Oxygen (4.7) > Build id: I20170524-2000 > (update 06/06/2017) > > System (uname -a) > Linux dhcp1100.se.dfs.de 4.11.3-200.fc25.x86_64 #1 SMP Thu May 25 19:03:07 > UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > > Most current Fedora 25 (update 06/06/2017) I have a similar setup: Build id: I20170530-0800 Linux fc25.x86_64 I can't seem to reproduce. Can you post *exact* steps to reproduce? What do you mean by "history" in the find part? Which Java do you use? If you're using Oracle java, can you try OpenJDK? It's possible that you're missing some java package, try installing all avaliable and relevant OpenJDK packages on your system. sudo dnf list installed | grep i openjdk java-1.8.0-openjdk.x86_64 1:1.8.0.131-1.b12.fc25 @updates java-1.8.0-openjdk-debuginfo.x86_64 java-1.8.0-openjdk-devel.x86_64 1:1.8.0.131-1.b12.fc25 @updates java-1.8.0-openjdk-headless.x86_64 1:1.8.0.131-1.b12.fc25 @updates java-1.8.0-openjdk-javadoc.noarch 1:1.8.0.131-1.b12.fc25 @updates java-1.8.0-openjdk-src.x86_64 1:1.8.0.131-1.b12.fc25 @updates
> I can't seem to reproduce. Can you post *exact* steps to reproduce? What do you > mean by "history" in the find part? Please look at the second attachment. The mouse is pointing to the "history". I mean the drop down menue, containing the search expressions, I used before. So opening find/replace, then opening the "history"/dropDownMenue. Results in the picture from the first attachement. > Which Java do you use? If you're using Oracle java, can you try OpenJDK? We use oracle java 1.8.131. I can not change that, due to company requirements. This afternoon we checked the (pretty) similiar environment of a co-worker. He can not reproduce the crash either. KDE settings? Docking Station? Multi monitor enviroment ?
(In reply to Sven Rathgeber from comment #7) > > I can't seem to reproduce. Can you post *exact* steps to reproduce? What do you > mean by "history" in the find part? > > Please look at the second attachment. The mouse is pointing to the "history". > I mean the drop down menue, containing the search expressions, I used before. > Ahhh. Cool, so we have a history, I never noticed this feature. With that said, the issue doesn't occur on my system. > > Which Java do you use? If you're using Oracle java, can you try OpenJDK? > We use oracle java 1.8.131. I can not change that, due to company > requirements. Do you still have openjdk installed? As oppose to setting java globally, you could try to tell Eclipse to launch via a specific java version: - edit eclipse.ini - *before* vmargs, add: (exactly as below, with new line) -vm PATH_TO_openJDK My path look like this: readlink -f /usr/bin/java | sed "s:jre/bin/java::" /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-1.b12.fc25.x86_64/ You can tell which java is used by eclipse via: jcmd # note pid of your eclipse jcmd PID VM.version > This afternoon we checked the (pretty) similiar environment of a co-worker. > He can not reproduce the crash either. > > KDE settings? Docking Station? Multi monitor enviroment ? You have KDE installed? ~I have never tested this. But it could be an issue. KDE uses QT as backend, where as Eclipse uses Gtk as backend. For Gtk to work on KDE, KDE creates an X11 Window and gives control to X11. This nesting might cause some issues. You could potentially try to kill KDE and launch a gnome instance and see if that's the cause of the problem. You could try using a single monitor to narrow down monitor. But I use 4 monitors (laptop + 3 external) and do not see such behaviour. Btw, since you're on KDE, I presume you're running X11 as backend? (as oppose to wayland). If on wayland, does this occur on X11 (on login screen of gnome, you can switch to 'classic' mode, which is x11). There might also be some issue with drawing libraries maybe.. Normally when eclipse crashes, there's a crash dump involved. jstack is there if Eclipse 'hangs' and you get a dump manually. Can you clarify, do you actually get a crash or does eclipse 'hang' for you? If you have a crash, do you have the .pid crash file at hand anywhere?
Created attachment 268801 [details] find history
What I tried so far. - installed GNOME -> same problem - used new, empty workspace -> NO problem .... I was wondering what is so special about my workspace. Hmm, the find history, since I used regular expressions. You asked wether it crashes or hangs. It hangs. Using kde it did not recover. But using gnome it recovers, giving me access to the history. The history is exploded. See attachment. Looks like the history, which consisted of several entries, is merged into one line. Can that cause the problem ?
Created attachment 268802 [details] Corrupt .metadata/.plugins/org.eclipse.ui.workbench.texteditor/dialag_settings.xml
I looked, where eclipse saves its find/replace history. .metadata/.plugins/org.eclipse.ui.workbench.texteditor/dialog_settings.xml I used this file in the new, emtpy workspace and can reproduce the bug. (attached dialog_settings.xml)
(In reply to Sven Rathgeber from comment #12) > I looked, where eclipse saves its find/replace history. > .metadata/.plugins/org.eclipse.ui.workbench.texteditor/dialog_settings.xml > > I used this file in the new, emtpy workspace and can reproduce the bug. > (attached dialog_settings.xml) With this, the issue reproduces. ~sort of. I get a popup that's huge, and it's content is a copy of my screen instead of the meue. I.e, no-functional. I think there's probably a limit on how big a menu item can be on gtk. Fix might be to force a maximum size on this one. We do something similar for shell: Bug 472743 – [GTK] Shell.setBounds() with specific values crashes JVM or makes the shell non functional I.e, we should investigate combo.add(), and see what length string causes breakage, and once found either report to gtk community and/or set a hard limit.
(In reply to Sven Rathgeber from comment #10) > What I tried so far. > > - installed GNOME -> same problem > - used new, empty workspace -> NO problem > > .... I was wondering what is so special about my workspace. Hmm, the > find history, since I used regular expressions. > Btw, thank you for savvy investigation & narrowing this down. It helped a lot.
Created attachment 268823 [details] Native snippet. Not tested myself, but my colleague said that if you change the 3rd invocation of: gtk_list_store_insert_with_values And make the string really really long: C 12345678901234 ... like 1000's of characters, Then gnome shell crashes. We should investigate if this is a known gtk bug, if not report it to gtk developers.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
