GNOME Bugzilla – Bug 607781
crash trying to cancel a mailbox update task
Last modified: 2010-01-28 07:02:13 UTC
I was trying to cancel a mailbox update task by clicking on the task's cancel button on the status bar and eventually got this crash:
+ Trace 220210
Thread 1 (Thread 31429)
During filing, bug 558079 was flagged as a candidate that this is a possible dup of. Unfortunately when being asked if they could be dups, one has lost all view of the bug being filed, including stack traces, etc. so it's difficult to try to "remember" what the one being filed looks like. I will leave it up to the experts to decide the duplicity. Please do feel free to close any of my bugs that you feel are duplicate. I would rather have the closed and pointed to the real bug than having duplicate copies of forty-eleven bugs open and not being assessed because they are duplicates of bugs that are being worked.
I think the trace is the same, what do you think? Akhil?, Milan?
It can be the same bug. There is an invalid msgport pointer in the bug 558079, but here are three different places where the crash could happen, namely: > Thread 22 (Thread 839): > #0 0x002a991b in camel_pstring_free (s=0x93713650 ".Ir9xcH_21978, > <435C366F075ED211B12200204840172D05869453@petitsuix.coe.int>") > at camel-string-utils.c:266 > > Thread 3 (Thread 31488): > #0 sYSMALLOc (av=..., bytes=...) at malloc.c:3410 > > Thread 1 (Thread 31429): > #0 0x0029b771 in camel_msgport_push (msgport=0x3ff00000, msg=0xb116bc0) > at camel-msgport.c:334 These three threads are doing something, where the rest are waiting only. This is the reason why I liked the old good gdb traces with <signal handler called> notes in them. One was able to see where exactly the signal was called (it used to be in more than one thread sometimes, in the crashing one, and in the main thread). Anyway, let's mark this as a duplicate, it would be quite good coincidence to have crashing in other threads and have the same Thread 1. *** This bug has been marked as a duplicate of bug 558079 ***