Closed
Bug 957540
Opened 11 years ago
Closed 9 years ago
Hang on shutdown when restarting Firefox for an update
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: whimboo, Unassigned)
Details
(Keywords: hang, perf)
Attachments
(1 file)
|
869.39 KB,
text/plain
|
Details |
I have already seen this a couple of times and it may be related to my strange memory conditions with unclassified heap memory as given on bug 751557.
I tried to apply the update to yesterdays Aurora build from my current build from 2014-01-02. The download and applying the update was successful, but when I triggered the restart Firefox never shutdown. I finally killed the process after 7 minutes. Firefox had a cpu load of about 400% all the time.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18440 henrik 20 0 3517m 2.1g 48m S 400.0 13.6 701:45.38 firefox
Attached you can find the log file from sysprof.
| Reporter | ||
Comment 1•11 years ago
|
||
Interestingly the syslog log shows some inode mismatches, here for libnspr4.so and libxul.so. Not sure if those are related to this problem. But more interesting is the mutex lock. Looks like we entered an infinite loop here?
| Reporter | ||
Updated•11 years ago
|
status-firefox28:
--- → affected
tracking-firefox28:
--- → ?
Keywords: hang
Summary: Restarting Firefox for an update the shutdown never happens → Hang on shutdown when restarting Firefox for an update
Version: 25 Branch → 28 Branch
Comment 2•11 years ago
|
||
I doubt this has anything to do with bug 751557, but the lock is suspicious.
Unfortunately that sysprof log doesn't tell much.
| Reporter | ||
Comment 3•11 years ago
|
||
What else should I do next time I get this hang? I don't run debug builds, so would a gdb output be helpful?
Comment 4•11 years ago
|
||
If the build has symbols, gdb would be still useful.
Comment 5•11 years ago
|
||
Moving to the component that is responsible for restarting
Component: Application Update → Startup and Profile System
Comment 6•11 years ago
|
||
How reproducible is this? Not clear that this is something our users are hitting widely - can Sumo also weigh in on any input that might correlate to this?
Flags: needinfo?(cwwmozilla)
Keywords: qawanted
This sounds like Aurora only? We don't get much Aurora input... This is also going to be a hard thing for users to report because it's on shutdown when most people are already shutting down their computers. If this is also Linux only, then we have no data. The last time we had non-spam input from Linux on 28 or 29 was in November.
The only thing I've found that seems kinda close is:
https://input.mozilla.org/en-US/dashboard/response/4144473
There are also general complaints of slowness, but I don't have enough data to say if that's significantly more than usual (I don't think so):
https://input.mozilla.org/en-US/dashboard/response/4137206
https://input.mozilla.org/en-US/dashboard/response/4137152
https://input.mozilla.org/en-US/dashboard/response/4134275
Flags: needinfo?(cwwmozilla)
Comment 8•11 years ago
|
||
I update Aurora every day on Ubuntu 13.04 32bit and didn't run into this issue once, so I guess it's not that reproducible. If anyone has more details about how to reproduce it than what's already in this report, let me know and I'll try that.
Keywords: qawanted
| Reporter | ||
Comment 9•11 years ago
|
||
This bug might also be related to hibernation mode given that I'm updating Firefox not that regularly. I put my box into sleep mode a couple of times a day. So it might be that after a couple of days we end up with this behavior.
Comment 10•11 years ago
|
||
This sounds like an edge case and not something we need to track for release.
| Reporter | ||
Comment 12•9 years ago
|
||
I actually haven't seen this problem for a while. So I would close this bug as WFM, and reopen in case I see it again.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(hskupin)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•