#2669 closed defect (worksforme)
xpra-client cores considerably with RubyMine and SublimeMerge
Reported by: | stdedos | Owned by: | stdedos |
---|---|---|---|
Priority: | major | Milestone: | 4.0 |
Component: | client | Version: | 3.0.x |
Keywords: | Cc: |
Description (last modified by )
I have seen a surge of 4.0 client cores these last few days. It could be that I'm using xpra more, or some changes are to blame for this.
I've sent you around 10~20 cores over e-mail; please process the application-specific cores first, and then descending on creation time.
Especially the RubyMine one comes for every other action.
Attachments (1)
Change History (14)
comment:1 Changed 2 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 2 years ago by
Summary: | xpra-client cores with RubyMine and SublimeMerge → xpra-client cores considerably with RubyMine and SublimeMerge |
---|
Changed 2 years ago by
Attachment: | redact-nemo-2669-display-_20_TIMESTAMP.log added |
---|
comment:4 Changed 2 years ago by
It turns out, that most of this (if not all) is mitigated by --opengl=no
.
I might be nice if you opened them to verify, but I guess for heavy seamless usage, I have to go OpenGL-less
comment:5 follow-up: 6 Changed 2 years ago by
Owner: | changed from Antoine Martin to stdedos |
---|
Intellij Tools crashes may be related to autocompletion.
Tooltips are known to cause problems with Intel opengl...
It turns out, that most of this (if not all) is mitigated by
--opengl=no
.
I am very tempted to switch the Intel
driver back to disabled by default.
The log you have added is a server log, so it won't have any client crash related info in it.
Even the crash logs are usually useless.
The only ways to debug opengl client crashes are:
- run with
-d all
and collect the end of all the crash lots to spot a pattern - run the client with
apitrace
comment:6 Changed 2 years ago by
Replying to Antoine Martin:
The only ways to debug opengl client crashes are:
- run with
-d all
and collect the end of all the crash lots to spot a pattern- run the client with
apitrace
If that's the only way, considering the Intel is already graylisted, it sounds too much hassle for both of us; taking also into account that maybe you cannot do anything about this Intel chipset just works badly with OpenGL.
Maybe I could try changing laptops altogether, but its battery life is just too amazing - even taking into account its quirks and issues.
You could re-use this ticket as a placeholder for opening the cores if you want; given all of what's said here, I don't see any meaningful way forward.
comment:8 Changed 2 years ago by
Replying to Antoine Martin:
#2721 may help.
This can be done on window-by-window basis? Waaau :-D
In any case - I assume this is a solely v4.x fix which I cannot install on my server 😕
However, I am planning a Ubuntu 16.04 direct-to 20.04.1 upgrade for my server (when it lands), so ... Hopefully in a month's time or so.
comment:9 Changed 2 years ago by
In any case - I assume this is a solely v4.x fix which I cannot install on my server 😕
This is scheduled for trac/milestone/3.1, but 3.1 is still a long way away.
comment:12 Changed 2 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Feel free to re-open if it still occurs with v4.
comment:13 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2669
One core that's unrelated to RubyMine / SublimeMerge is this coming from Nemo file manager (Split from Nautilus):
And the client died almost immediately after that. Attaching full server also; idk if it's wise to truncate it or not.