Bug #5073

[norepro] crash around "g_signal_handlers_disconnect_matched"

Added by Charles Lindsay about 1 year ago. Updated about 1 month ago.

Status:Invalid Start date:04/17/2012
Priority:Urgent Due date:
Assignee:- % Done:

0%

Category:-
Target version:0.1
Keywords:

Description

I was selecting different folders in somewhat rapid succession trying to recreate #5072, when I got a totally new crash due to an assertion failure:

(geary:13105): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(geary:13105): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(geary:13105): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(geary:13105): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Segmentation fault (core dumped)

Once again I have a coredump and DB file to aid in debugging.


Related issues

related to geary - Bug #6620: [norepro] crash in nonblocking semaphore wait's signal ha... Fixed 03/20/2013

History

Updated by Charles Lindsay about 1 year ago

Note I was on commit 875d421.

Updated by Adam Dingle about 1 year ago

  • Priority changed from Normal to High
  • Target version set to 0.1

Updated by Jim Nelson about 1 year ago

  • Category set to 13
  • Priority changed from High to Urgent

Updated by Adam Dingle about 1 year ago

  • Subject changed from crash around "g_signal_handlers_disconnect_matched" to [norepro] crash around "g_signal_handlers_disconnect_matched"

Updated by Adam Dingle about 1 year ago

  • Status changed from Open to 5
  • Resolution set to worksforme

Closing for now since we can't reproduce this.

Updated by Charles Lindsay about 1 month ago

  • Status changed from 5 to Invalid

Also available in: Atom PDF