Bug 2391

Summary:

xcompmgr-1.1.1 segmentation fault when a window is destroyed while xscreensaver is running

Product:

xorg

Reporter:

Jonathan Briggs <zlynx>

Component:

App/xcompmgr

Assignee:

Xorg Project Team <xorg-team>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

high

CC:

dberkholz

Version:

unspecified

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
patch to fix use-after-free bug	none

Description Jonathan Briggs 2005-01-27 01:33:08 UTC

I managed to reproduce it by running:

# xcompmgr -c -C -f -F
# sleep 7; gnome-terminal; exit

and then clicking my Lock screensaver icon.  After waiting 7 seconds I would
unlock the screen and xcompmgr would crash.  xcompmgr must be running with fade
options.

I have a patch that fixes it so that dequeue_fade and its callbacks (which might
free important data) are run last in run_fades.

Comment 1 Jonathan Briggs 2005-01-27 01:34:37 UTC

Created attachment 1757 [details] [review]
patch to fix use-after-free bug

Comment 2 Adam Jackson 2005-01-27 13:20:50 UTC

applied, thanks!  i'll package up 1.1.2 sometime tonight.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.