After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 710050 - window_backed_app_get_window lets shell crashes sometimes
window_backed_app_get_window lets shell crashes sometimes
Status: RESOLVED DUPLICATE of bug 674799
Product: gnome-shell
Classification: Core
Component: overview
3.10.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 710051 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-10-13 18:30 UTC by Maximilian Ruta
Modified: 2015-10-08 03:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Maximilian Ruta 2013-10-13 18:30:10 UTC
Sometimes my GNOME Shell just crashes and prints out:

ERROR:shell-app.c:149:window_backed_app_get_window: assertion failed: (app->runnig_state)

I think this could be a part of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=905914
Or this commit: https://mail.gnome.org/archives/commits-list/2011-August/msg06567.html

I can not assign this behavior to an action but i think it appears most times if i want to access the activity panel.
Comment 1 drago01 2013-10-20 11:13:48 UTC
*** Bug 710051 has been marked as a duplicate of this bug. ***
Comment 2 heresomename 2014-01-29 13:10:37 UTC
I have same problem with 3.10.2. gnome-shell crashes occasionally:

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #1 __GI_abort
    at abort.c line 89
  • #2 _g_log_abort
    at gmessages.c line 255
  • #3 g_assertion_message
  • #4 g_assertion_message_expr
    at gtestutils.c line 2293
  • #5 window_backed_app_get_window
    at shell-app.c line 149
  • #6 shell_app_launch
    at shell-app.c line 1203
  • #7 shell_app_activate_full
    at shell-app.c line 636
  • #8 ffi_call_unix64
    at ../../../libffi/src/x86/unix64.S line 75
  • #9 ffi_call
    at ../../../libffi/src/x86/ffi64.c line 492
  • #10 gjs_invoke_c_function
    at gi/function.c line 894
  • #11 function_call
    at gi/function.c line 1203
  • #12 CallJSNative
    at ./jscntxtinlines.h line 372
  • #4 g_assertion_message_expr
    at gtestutils.c line 2293

Comment 3 Christian Kirbach 2014-02-01 13:30:55 UTC
i got this when clicking on the evolution calendar notification at the bottom. From the trace I can guess it was trying to launch evolution.
I have installed the missing debug symbols and retraced the coredump. this trace should be ... helpful :)


Thread 1 (Thread 0x7f33413ada00 (LWP 1994))

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #1 __GI_abort
    at abort.c line 90
  • #2 _g_log_abort
    at /build/buildd/glib2.0-2.38.2/./glib/gmessages.c line 255
  • #3 g_assertion_message
  • #4 g_assertion_message_expr
    at /build/buildd/glib2.0-2.38.2/./glib/gtestutils.c line 2293
  • #5 window_backed_app_get_window
    at shell-app.c line 149
  • #6 shell_app_launch
    at shell-app.c line 1203
  • #7 shell_app_activate_full
    at shell-app.c line 636
  • #8 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #9 ffi_call
    at ../src/x86/ffi64.c line 522
  • #10 ??
    from /usr/lib/libgjs.so.0
  • #11 ??
    from /usr/lib/libgjs.so.0
  • #12 CallJSNative
    at ./jscntxtinlines.h line 372
  • #13 js::InvokeKernel
    at /build/buildd/mozjs17-17.0.0/js/src/jsinterp.cpp line 345
  • #14 js::Interpret
    at /build/buildd/mozjs17-17.0.0/js/src/jsinterp.cpp line 2414
  • #15 UncachedInlineCall
    at /build/buildd/mozjs17-17.0.0/js/src/methodjit/InvokeHelpers.cpp line 327
  • #16 js::mjit::stubs::UncachedCallHelper
    at /build/buildd/mozjs17-17.0.0/js/src/methodjit/InvokeHelpers.cpp line 410
  • #17 UncachedLoweredCall
    at /build/buildd/mozjs17-17.0.0/js/src/methodjit/InvokeHelpers.cpp line 375
  • #18 js::mjit::stubs::CompileFunction
    at /build/buildd/mozjs17-17.0.0/js/src/methodjit/InvokeHelpers.cpp line 239
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??

Comment 4 Christian Kirbach 2014-02-01 13:31:39 UTC
(gdb) frame 6
  • #6 shell_app_launch
    at shell-app.c line 1203
$1 = {parent = {g_type_instance = {g_class = 0x33a4fc0}, ref_count = 2, qdata = 0x3cf1ff1}, started_on_workspace = 0, 
  state = SHELL_APP_STATE_STOPPED, entry = 0x0, running_state = 0x0, window_id_string = 0x2c11c30 "window:3", 
  casefolded_name = 0x0, casefolded_generic_name = 0x0, name_collation_key = 0x0, casefolded_exec = 0x0, 
  casefolded_keywords = 0x0}
(gdb) p error
$2 = (GError **) 0x7fff1121dbc8
(gdb) p *error
$3 = (GError *) 0x0
Comment 5 Christian Kirbach 2014-02-01 13:37:37 UTC
Evolution never started for me, and in frame 5 gnome-shell is trying to determine which window some app has.
Comment 6 Owen Taylor 2015-10-08 03:01:47 UTC

*** This bug has been marked as a duplicate of bug 674799 ***