Closed
Bug 903011
Opened 11 years ago
Closed 2 years ago
Firefox still seems to be unresponsive occasionally when starting with the profiler
Categories
(Core :: Gecko Profiler, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: wlach, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
We now have profiling working with Eideticker for the Galaxy Nexus, but it still seems to be hanging on startup occasionally (to the point where we rarely seem to make it through a full run).
Here's a logcat of a failing run from last night.
|
Reporter | |
Updated•11 years ago
|
|
||
Comment 1•11 years ago
|
||
Is there a particular test that's more prone to this? I haven't been able to reproduce it on my Galaxy Nexus.
Flags: needinfo?(wlachance)
|
|
Reporter | |
Comment 2•11 years ago
|
||
Here's the last 7 failures (in 9 days)
cnn
nytimes-scroll
startup-abouthome-fresh
taskjs
cnn
nytimes-zoom
taskjs
Looks like cnn and taskjs are the ones that fail more often
Flags: needinfo?(wlachance)
This is a very old bug, and things have changed a lot. If you still see the same issue, please re-open/re-file.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•