GNOME Bugzilla – Bug 437078
Crash in wnck_window_get_transient()
Last modified: 2008-02-01 06:32:23 UTC
Version: 2.18.0 What were you doing when the application crashed? this crash often happens when I am quitting a full screen window java application and happens with FC6 and FC7(rawhide) Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 61112320 vsize: 61112320 resident: 14024704 share: 9887744 rss: 14024704 rss_rlim: 4294967295 CPU usage: start_time: 1178690599 rtime: 182 utime: 136 stime: 46 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208535328 (LWP 4616)] (no debugging symbols found) 0x00116402 in __kernel_vsyscall ()
+ Trace 133205
Thread 1 (Thread -1208535328 (LWP 4616))
----------- .xsession-errors (98 sec old) --------------------- Window manager warning: Treating resize request of legacy application 0x3c00020 (Live Visio) as a fullscreen request Window manager warning: Treating resize request of legacy application 0x400000a (Vision) as a fullscreen request Window manager warning: Treating resize request of legacy application 0x4000015 (Live Visio) as a fullscreen request Window manager warning: Treating resize request of legacy application 0x400001a (Live Visio) as a fullscreen request Window manager warning: Treating resize request of legacy application 0x400001f (Live Visio) as a fullscreen request ** (gnome-system-monitor:5881): WARNING **: SELinux was found but is not enabled. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e001ac specified for 0x2e001b1 (IDE Shutdo). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e001ac specified for 0x2e001b1 (IDE Shutdo). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e001ac specified for 0x2e001b1 (IDE Shutdo). ** Message: Found best visual for GL: 0x21 ** (gnome-system-monitor:6226): WARNING **: SELinux was found but is not enabled. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 87926 [details] same error (from a different computer) with extra debugging info I have redone the crash with more debugging info, hopefully this will give you the information you need to solve the problem.
Ah, that's a bit better. Do you have the possibility to install the debugging info for libwnck too?
Created attachment 87987 [details] debug info with the libwnck more information as requested.
Thanks for your help. We'll look into this? Is the java application freely available, in case we need to reproduce the crash?
Created attachment 88055 [details] java code to reproduce the crash The attached simple java code causes the crash, it appears the the java call gd.isFullScreenSupported seems to be partly causing the crash as I could not reproduce the crash without it. Also note that I have been running this with multiple monitors so I don't know if it also occurs in a single monitor environment.
Thanks. I quickly tried, but it doesn't make anything crash here. I'm not quite sure how the crash is happening: it means we'd have, in wnck_tasklist_active_window_changed(), wnck_window_get_transient() which returns something that is not NULL and not a WnckWindow. But this functions either returns NULL or what's returned by g_hash_table_lookup(), which, AFAICT, is always something that is a WnckWindow (or NULL). Maybe someone else would have a better idea of what's wrong?
*** Bug 447141 has been marked as a duplicate of this bug. ***
Putting the interesting part of the stack trace as a comment...
+ Trace 141218
Just wondering: are you using a multihead setup? If yes, then this might be related to bug 447387.
(In reply to comment #10) > Just wondering: are you using a multihead setup? If yes, then this might be > related to bug 447387. > Yes, this problem occurs with multihead setup. I will check when I get the fix noted in that bug and see if it solves the problem.
Okay, marking as NEEDINFO then, until you can test with libwnck >= 2.19.4.
*** Bug 452366 has been marked as a duplicate of this bug. ***
*** Bug 473325 has been marked as a duplicate of this bug. ***
*** Bug 513515 has been marked as a duplicate of this bug. ***