https://bugzilla.novell.com/show_bug.cgi?id=283914 phdm@macqel.be changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|phdm@macqel.be | ------- Comment #2 from phdm@macqel.be 2007-06-14 01:51 MST -------

From the documentation of John Bradley's xv :

"It is occasionally desirable to reload an image file because the contents of the file have changed. For example, [...] you have a program that generates images, and you d like to view these images without any manual intervention. xv provides a way to reload an image via an external signal. If you send the xv process a SIGQUIT signal ( kill -QUIT <pid> , or kill -3 <pid> on most systems), the program will reload the currently selected file." Up to now, this used to work perfectly. In opensuse 10.3, when I do the same (i.e. kill -QUIT <xv-pid>), the `xv' process begins to use 100% cpu time instead of displaying the new image. I surmise the problem arises from the replacment of libX11 by an xcb-ified version of libX11. I even replaced libX11 by opensuse 10.2's libX11 and kill -QUIT xv works perfectly again, so that shows that the problem lies in 10.3's libX11 or in xcb. How to reproduce summary : start xv with an image file to display : xv image.jpg & send the QUIT signal to xv (this should tell xv to reread and redisplay image.jpg): killall -QUIT xv xv now uses 100% CPU time :( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283914 ------- Comment #4 from sndirsch@novell.com 2007-06-14 03:45 MST ------- Hmm. Downgrading xv to the openSUSE 10.2 version didn't help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283914 ------- Comment #6 from werner@novell.com 2007-06-14 04:05 MST ------- Agree, on 10.2 this does not happen .. what does the libxcb do on SIGQUIT? An "strace -f -p `pidof xv`" shows nothing, but where from the load is enforced? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283914 ------- Comment #8 from werner@novell.com 2007-06-14 04:25 MST ------- Beside this a `killall -15 xv' does not help after the SIGQUIT. The xv process is deadlocked. An "strace -f -p `pidof xv`" shows during the "killall -3 xv" the following: 18042 select(4, [3], [], NULL, NULL) = ? ERESTARTNOHAND (To be restarted) 18042 --- SIGQUIT (Quit) @ 0 (0) --- 18042 select(4, [3], [3], NULL, NULL) = 1 (out [3]) 18042 writev(3, [{"\224\10\7\0\0\1\7\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 28}], 1) = 28 seems that writing on the socket is brocken, that is that the socket is closed without confirmation and further writing will block xv. On 10.2 the socket is not closed and therefore the xv can use write(v) on the socket. Note, that xv uses SIGQUIT to relaod images, but libxcb on STABLE ignores the signal handler used by xv. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283914 ------- Comment #10 from werner@novell.com 2007-06-14 09:03 MST ------- Nevertheless, the socket is closed by this signal ... which function of the libxcb or libX11 or libX11-xcb can do this within the signal handler of xv? Btw: sometimes I can not reproduce this on 10.3, in other words sometimes SIGQUIT does not close the socket. Do we see a race triggered by the usage of X11 function within a signal handler? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283914#c12 --- Comment #12 from Stefan Dirsch 2007-07-04 04:58:50 MST --- It's indeed xcb related. Building libX11 without xcb no longer results in xv consuming 100%CPU after invoking "killall -3 xv" and the picture gets reloaded! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914#c16 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfabian@novell.com Summary|libX11/libxcb uses 100% CPU |libX11/libxcb uses 100% CPU time after killall - |time after killall -3 xv |3 xv / killall -2 xv (Ctrl-C) --- Comment #16 from Stefan Dirsch 2007-07-12 04:58:21 MST --- Same issue with "killall -2 xv" (Ctrl-C). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914#c17 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@novell.com --- Comment #17 from Stefan Dirsch 2007-08-13 09:23:00 MST --- *** Bug 299820 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=299820 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914#c20 --- Comment #20 from Stefan Dirsch 2007-08-24 03:42:17 MST --- Email (thread) on xcb ML: http://lists.freedesktop.org/archives/xcb/2007-August/002966.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914#c22 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@novell.com --- Comment #22 from Stefan Dirsch 2007-09-05 09:18:45 MST --- *** Bug 307797 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=307797 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914#c24 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Minor Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #24 from Dr. Werner Fink 2007-10-08 08:15:21 MST --- xv is not developed active anymore, sorry but I'll not rewrite xv. Beside this: why there is no warning about `do not use Xlib out from signal handlers'. AFAICS there is no warning nor any other comment about such an issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=283914#c28 Mike Fabian changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asklein@wpax13.physik.uni-wuerzburg.de --- Comment #28 from Mike Fabian 2008-05-21 08:54:43 MST --- *** Bug 393085 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=393085 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=283914#c30 --- Comment #30 from Dr. Werner Fink 2008-05-23 05:48:13 MST --- Created an attachment (id=217762) --> (https://bugzilla.novell.com/attachment.cgi?id=217762) xv-3.10a-signal.dif Moved xv from XNextEvent() to XtAppNextEvent(), this requires the usage of XtToolkitInitialize(), XtCreateApplicationContext(), and XtDisplayInitialize() but enables me to use XtAppAddSignal() before setting up a signal handler and then use XtNoticeSignal() instead of the original signal handler. With this it seems to work now. Nevertheless it is very annoying the standard X11 library libx11 does not provide this possiblity and the X11 tool library is the only way to set up such things. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=283914 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=283914#c32 --- Comment #32 from Stefan Dirsch 2008-05-23 05:55:59 MST --- Thanks a lot, Werner! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.