Closed Bug 494849 Opened 15 years ago Closed 14 years ago

Freezing after wake from sleep [Mac]


(Thunderbird :: General, defect)

Not set


(Not tracked)



(Reporter: gkw, Assigned: Bienvenu)



(Keywords: hang, qawanted)


(2 files)

I get this really occasionally - have a hang stack. Basically my MBP went to sleep and when I wake it (after quite a number of hours), debug Thunderbird is freezing.

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090523 Lightning/1.0pre Shredder/3.0b3pre

This doesn't happen often. I re-tried again and it doesn't hang after that. Hopefully the stack is useful.
Attaching this in case either stack might be useful.
(In reply to comment #0)
> Created an attachment (id=379647) [details]
> stack from running `thread apply all bt` in gdb

This is the part that seems suspicious:

Thread 6 (process 950 thread 0x6903):
#0  0x00000000 in ?? ()
Cannot access memory at address 0x4

bienvenu, any idea what's going on, is this worth nominating for blocking?
Flags: wanted-thunderbird3?
Sidenote on how to get a hang stack using gdb:

If running debug thunderbird, either clicking Sample Process in activity manager will get a sample, or follow the following (slightly modified, original credit Steven Michaud) instructions from bug 470001 comment 23 :

1) Run Shredder.

2) Do 'ps ax | grep thunderbird' at a Terminal prompt to find its
   process id.

   The pid will be listed in the first column to the left.  Let's
   assume it's '123'.

3) Do 'gdb thunderbird 123' to attach to the Shredder process.

Additional step:

4) Do 'thread apply all bt' to get a backtrace of all running TB threads, then attach the output to a bug report here in b.m.o
(In reply to comment #3)
> Sidenote on how to get a hang stack using gdb:

(Has been transferred to a wiki page at )
I think thread 1 and thread 13 are blocking each other - I don't know about the thread that crashed with a 0+4 deref - there's not enough info in the stack there.
Interestingly, I put my laptop to sleep etc quite a few times over last weekend (Thur-Sunday) and didn't see this at all.
The way I get this is by closing the screen - that's the way I put my laptop to sleep. Sometimes when I wake it up - the next morning or a bit later Tb is hanged.
The profile as 2 gmail accounts, 2 newsgroup accounts, and one RSS/blog.
putting in b4
Assignee: nobody → bienvenu
Flags: wanted-thunderbird3? → blocking-thunderbird3+
Target Milestone: --- → Thunderbird 3.0b4
The Thunderbird drivers wish to release Thunderbird 3 as soon as possible. As a result, we feel that this bug shouldn't stand in the way of all the other good work getting into the hands of users sooner rather than later. Therefore we are retargeting it for 3.1. See for more details. The 3.1 release is expected to be a quick release soon after Thunderbird 3.
Flags: blocking-thunderbird3+ → blocking-thunderbird3-
Target Milestone: Thunderbird 3.0b4 → ---
Flags: blocking-thunderbird3.1+
is this still seen with trunk builds?

related?  Bug 536155 -  Thunderbird hangs on Get Mail from a IMAP account when waking from sleep.
Summary: Freezing after wake from sleep → Freezing after wake from sleep [Mac]
Since this doesn't appear to be a regression from Thunderbird 2, and it seems to be effecting a very small number of users, I don't think this wants to block Tb 3.1, so minusing.  bienvenu, feel free to change if you disagree...
Flags: wanted-thunderbird+
Flags: blocking-thunderbird3.1-
Flags: blocking-thunderbird3.1+
This falls into the category of bugs that I would probably block on if I could reproduce them. It's not at all clear that it's not a regression from TB 2, though TB 2 probably had a separate set of issues.
Adding qawanted in the hopes of finding steps to reproduce.  If those appear, this should be nominated to block whatever release is current.
Flags: blocking-thunderbird3.1-
Keywords: qawanted
I think this has largely WFM since. Been running 3.0.4 without issue for some weeks and only just shifted to Lanikai.
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.