Re: sawfish + xinerama dropping / unmapping windows

Janek Kozicki said:     (by the date of Thu, 22 Oct 2009 22:14:32 +0200)

> Tell me how to proceed with debugging.
> I can run sawfish in valgrind (will try doing so). I'm not sure if
> I could get libXinerama to run inside valgrind.

I tried with valgrind: no errors whatsoever. sawfish is totally
clean, and there is no undefined behaviour. Here's what I get in valgrind:
(the text after # are my comments).

==5328== Memcheck, a memory error detector
==5328== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==5328== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info
==5328== Command: /usr/bin/sawfish
*** File error: No such file or directory, sawmill-defaults
*** Unbound variable: edge
(You're accessing an undefined variable or function `edge')
   # some ,,standard'' sawfish error, I always have it.

PID: 5337
sawfish-pager is running, stopping: 5337
   # my script to toggle on/off the pager is very talkative

Xlib:  extension "RANDR" missing on display ":0.0".
   # I just started firefox and several random windows have just disappeared.
   # this time it was: 
   # - the root window with background image (so now the background is plain gray), 
   # - claws-mail
   # - couple of xterms
   # rox-panel
   # This RANDR error is coming from very talkative firefox. I have no RANDR with xinerama

warning: failed to allocate a window
warning: failed to allocate a window
warning: failed to allocate a window
   # I tried renaming some files with rox ;)
   # next I quit sawfish

==5328== HEAP SUMMARY:
==5328==     in use at exit: 3,345,976 bytes in 10,671 blocks
==5328==   total heap usage: 105,672 allocs, 95,001 frees, 15,397,129 bytes allocated
==5328== LEAK SUMMARY:
==5328==    definitely lost: 5,908 bytes in 68 blocks
==5328==    indirectly lost: 7,504 bytes in 237 blocks
==5328==      possibly lost: 280,647 bytes in 2,737 blocks
==5328==    still reachable: 3,051,917 bytes in 7,629 blocks
==5328==         suppressed: 0 bytes in 0 blocks
==5328== Rerun with --leak-check=full to see details of leaked memory
==5328== For counts of detected and suppressed errors, rerun with: -v
==5328== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 152
from 50)

Do you have some other hints about what to check?

Janek Kozicki                                                         |

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]