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 740996 - Crash in g_type_check_instance()
Crash in g_type_check_instance()
Status: RESOLVED DUPLICATE of bug 740841
Product: gnome-shell
Classification: Core
Component: general
3.14.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-12-01 18:46 UTC by Milan Bouchet-Valat
Modified: 2014-12-02 13:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2014-12-01 18:46:34 UTC 
This has been reported twice on Fedora 21. Not sure how to reproduce it, though it appeared after resuming from suspend here.

https://bugzilla.redhat.com/show_bug.cgi?id=1149565

+ Trace 234387

Thread 1 (Thread 0x7f4f594c1a40 (LWP 7588))

  • #0 g_type_check_instance
    at gtype.c line 4085
  • #1 g_signal_handler_disconnect
    at gsignal.c line 2566
  • #2 check_connectivity_data_free
    at nm-client.c line 1470
  • #3 clear_op_res
    at gsimpleasyncresult.c line 245
  • #4 g_simple_async_result_finalize
    at gsimpleasyncresult.c line 265
  • #5 g_object_unref
    at gobject.c line 3170
  • #6 release_native_object
    at gi/object.cpp line 1107
  • #7 object_instance_finalize
    at gi/object.cpp line 1428
  • #8 finalize
    at /usr/src/debug/mozjs-24.2.0/js/src/jsobjinlines.h line 213
  • #9 finalize<JSObject>
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 331
  • #10 FinalizeTypedArenas<JSObject>
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 395
  • #11 FinalizeArenas
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 432
  • #12 finalizeNow
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 1306
  • #13 js::gc::ArenaLists::queueObjectsForSweep
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 1402
  • #14 BeginSweepingZoneGroup
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 3677
  • #15 BeginSweepPhase
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 3761
  • #16 IncrementalCollectSlice
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 4289
  • #17 GCCycle
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 4422
  • #18 Collect
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 4558
  • #19 Collect
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 1998
  • #20 GCSlice
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 4594
  • #21 js::MaybeGC
    at /usr/src/debug/mozjs-24.2.0/js/src/jsgc.cpp line 1992
  • #22 JS_MaybeGC
    at /usr/src/debug/mozjs-24.2.0/js/src/jsapi.cpp line 2715
  • #23 gjs_schedule_gc_if_needed
    at gjs/jsapi-util.cpp line 1251
  • #24 gjs_call_function_value
    at gjs/jsapi-util.cpp line 749
  • #25 gjs_closure_invoke
    at gi/closure.cpp line 284
  • #26 closure_marshal
    at gi/value.cpp line 160
  • #27 g_closure_invoke
    at gclosure.c line 768
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3553
  • #29 g_signal_emit_valist
    at gsignal.c line 3309
  • #30 g_signal_emit
    at gsignal.c line 3365
  • #31 meta_screen_restacked
    at core/screen.c line 2981
  • #32 meta_stack_tracker_sync_stack
    at core/stack-tracker.c line 870
  • #33 stack_tracker_sync_stack_later
    at core/stack-tracker.c line 876
  • #34 run_repaint_laters
    at core/util.c line 809
  • #35 _clutter_run_repaint_functions
    at ./clutter-main.c line 3643
  • #36 master_clock_update_stages
    at ./clutter-master-clock.c line 457
  • #37 clutter_clock_dispatch
    at ./clutter-master-clock.c line 595
  • #38 g_main_dispatch
    at gmain.c line 3111
  • #39 g_main_context_dispatch
    at gmain.c line 3710
  • #40 g_main_context_iterate
    at gmain.c line 3781
  • #41 g_main_loop_run
    at gmain.c line 3975
  • #42 meta_run
    at core/main.c line 473
  • #43 main
    at main.c line 463 






Comment 1


Milan Bouchet-Valat





          2014-12-01 18:49:28 UTC
        



Actually it appears I've seen it twice here, so it might be reproducible.






Comment 2


Rui Matos





          2014-12-02 13:03:37 UTC
        



The trace seems like the one in bug 740841






Comment 3


Milan Bouchet-Valat





          2014-12-02 13:16:37 UTC
        



Yes, right. Funny it doesn't always give the same crash. Memory corruption?

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