-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Linux] IDE crashes one time a day #592
Comments
Can you please share information about the Linux distribution you're using and version of gtk and family? |
This could be either Ubuntu specific GTK problem, or Wayland you are using. |
The issue is in Pango integration (pango_attr_list_unref) and SWT hasn't been updated to latest Pango changes so I highly doubt this is WM related issue. |
OS :
libgtk :
libpango :
|
Interesting, this is far older pango than I expected (although 1.44 is where our issues started) . This makes me think in another direction - Do you by any chance changed the Gtk theme used? Can you try whether switching to Adwaita keeps the issue present? |
Sorry if my response is not the expected one, I'm really not a Linux expert. As graphic environnement I'm running xfce or KDE Plasma Desktop and I encounter the problem with both.
|
Verify you actually use adwaita gtk theme for an experiment as described at https://www.omgubuntu.co.uk/2019/04/how-to-try-the-new-adwaita-theme-on-ubuntu-19-04 |
Ok, I'm on Breeze theme ! I'm switching to Adwaita and I'll keep you up to date. |
Ok, that was fast :') |
Unfortunately, I can't find anything helpful in the log. |
The code mentioned in callstack is executed whenever editing caret moves to a new line is source code editor. |
Can I do something on my side to investigate further ? Enable some debug trace, or run a tool to get more information when it happens ? |
Let's capture a core dump to investigate further. Note that this core dump will contain everything Eclipse knew at the moment of crash, including parts of source files, passwords, etc. If you're working on something private, you might want to create an empty workspace and reproduce the crash on some opensource code. If you don't know how to reproduce crash quickly, you might want to install OBS-Studio and record your screen during your working days. When it crashes, check what exactly you did just before the crash and try to repeat it with exactly same source file / line.
|
Hi, don't know if this is the same problem as usual but got this when it happend today :
No core dump written. But it's strange I don't have any hs_err_pid file either. |
This one is referenced here : But no one tell about a total crash of Eclipse. |
What crashes JVM is Similar crash was reported in other applications too, like
The last link gives some hints, feel free to try them out, I'm not familiar with this code & haven't seen such crashes yet. |
Did you have any crashes (with |
Hi ! got this one today :) Unfortunately I don't find any core dump at the specified location :s |
Most of the time, it crashes whith only this message : No pid log file or core dump... |
It seems that something is corrupting memory in Eclipse, which manifests as various random crashes. I guess we'll have to resort to memory verifier, now that attempts to catch a core dump didn't succeed. Please do the following to build it:
Then, run Eclipse this way:
If you do it correctly, you should see additional headers printed to console when running Eclipse. |
Ok I'll try that. Does this can expose sensitive data I'm working on or it will only record technical information ? |
The core dump will contain everything that Eclipse had in memory, which could contain various sensitive information. The |
Hi,
At least since 2022-12 update, Eclipse crashes few minutes after the first launch of the day.
I know it's kinda weird but after I relaunch it, I have no more problem for the rest of the day :s
I'm just launching my IDE, start to work, and after some random time but not more than an hour, the IDE is closing itself.
hs_err_pid228593.log
metadata.log
Tell me if you need more log.
Regards,
Clément.
The text was updated successfully, but these errors were encountered: