Closed
Bug 1121407
Opened 9 years ago
Closed 9 years ago
Gecko Profiler causes immediate crash on Nightly x64 only
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1120126
People
(Reporter: sdl, Unassigned)
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36 Steps to reproduce: Have noticed a substantial performance degradation in Firefox which seems to coincide with the update to the 38 Branch of Firefox Nightly (v38.0a1 2015-01-13 Win64). Attempted to get some useful diagnostic data for reporting in a bug by installing the Gecko Profiler extension as per: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem Actual results: Firefox Nightly immediately crashed on installing the extension. On subsequent attempts to restart Firefox the browser also immediately crashed. To recover the extension had to be manually removed from the user profile extensions folder. Crash on install: https://crash-stats.mozilla.com/report/index/f87d6881-d4c1-4886-8c12-d32922150114 Crash on restart: https://crash-stats.mozilla.com/report/index/f47ddfaf-4432-47cb-85b6-f2d692150114 The stack traces appear identical. Expected results: Extension successfully installs & functions to obtain performance profiling data.
Updated•9 years ago
|
Summary: Gecko Profiler causes immediate crash on Nightly → Gecko Profiler causes immediate crash on Nightly x64 only
Comment 2•9 years ago
|
||
I don't have the bandwidth to address unwinding on win x64. For now I'd recommend using a windows native profile. I know memshrink is working on it for DMD so perhaps once they get it working this will become easier.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(bgirard)
Comment 3•9 years ago
|
||
Nightly 38.0a2 x64 (2015-01-13) crashes immediately. However, Nightly 38.0a2 x64 (2015-01-14) does not crash. Reporter, could you re-test in Latest Nightly?
Flags: needinfo?(samuel.denbigh.leslie)
Comment 4•9 years ago
|
||
Sorry s/38.0a2/38.0a1/
Comment 5•9 years ago
|
||
This should be fixed by Bug 1120126
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Flags: needinfo?(samuel.denbigh.leslie)
You need to log in
before you can comment on or make changes to this bug.
Description
•