#2328 closed defect (fixed)
ubuntu 16.04 python3 shadow server segfault on exit
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 3.0 |
Component: | server | Version: | 2.5.x |
Keywords: | Cc: |
Description
Discovered whilst testing for #2296.
Only seems to affect Ubuntu 16.04: also tested on Fedora and Ubuntu 18.04.
The server segfault can be triggered from both xpra stop
and the exit-with-client
switch.
Change History (5)
comment:1 Changed 22 months ago by
Status: | new → assigned |
---|
comment:2 Changed 22 months ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The crash is triggered by close_gtk_display
.
Skipping this cleanup step with XPRA_CLOSE_GTK_DISPLAY=0
fixes the problem.
r22928 re-orders the cleanup code (related, but not a fix for this crash).
r22929 + r22930 just skips closing the display for python3 shadow servers on Ubuntu 16.04 only!
(note: this cleanup code runs more than once, but that's not the cause of the crash)
comment:4 Changed 11 months ago by
The default has been changed due to more crashes in Ubuntu 20.04: ticket:2761#comment:3.
comment:5 Changed 3 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2328
One does not need to ever have connected a client to trigger the segfault, which should rule out x11 shared memory race conditions during cleanup.
Still occurs when running with minimal features enabled:
(though I did find a bug along the way: r22927)
Backtrace from gdb: