Open Bug 802798 Opened 12 years ago Updated 2 years ago

crash in addProfileEntry @ js::PCToLineNumber

Categories

(Core :: Gecko Profiler, defect, P3)

Product:
Core
Component:
Gecko Profiler
Type:
defect

Tracking

()

Status:
REOPENED

People

(Reporter: KWierso, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, reproducible, Whiteboard: qa-not-actionable)

Crash Data

This bug was filed from the Socorro interface and is report bp-cb9db94e-9273-4ab6-8613-0b6522121017 . ============================================================= I got this crash by enabling the previously-disabled Profiler extension. I was going to capture a profile of a performance issue I have with long running browser sessions, but now I need to wait for my newly restarted session to experience those problems. After restarting from the crash, the Profiler extension IS enabled, and running correctly, so I'm guessing the problem came from enabling it while in my badly-performing session.
Crash Signature: [@ js::PCToLineNumber(unsigned int, unsigned char*, unsigned char*, unsigned char*, unsigned int*)] → [@ js::PCToLineNumber(unsigned int, unsigned char*, unsigned char*, unsigned char*, unsigned int*)] [@ js::PCToLineNumber]
OS: Windows 8 → All
Hardware: x86 → All
Keeps happening to me on my OS X machine :(
js unwinding with ion crashes after about 5 seconds coming out of private browsing. not sure if its this signature.
Got anyone to look at this Nicolas? I think this is a bug disabling/enabling profiling with IonMonkey.
Depends on: 736299
Keywords: reproducible
I crashed here while attaching a patch to bugzilla (Win7x64).
I can occasionally reproduce with Nightly on OSX after exited PB mode: https://crash-stats.mozilla.com/report/index/bp-165b870e-fe30-459d-8236-a1a3a2121204
I used to get this often but I haven't got it in 20+ and can't find any reports. Please re-open if we can find recent signatures.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
I just hit this crash on a Nightly from Jan 19th: https://crash-stats.mozilla.com/report/index/bp-6d492033-4d6a-4153-9916-912aa2130119
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
hit this today while enabling the profiler. After i sent the crash report, the profile manager opened, asking me to choose a profile to use. http://crash-stats.mozilla.com/report/index/bp-4b232789-2e18-41c3-a81a-e30da2130125
Right at this moment, I'm hitting the bug at <http://appleinsider.com/articles/13/06/14/att-to-add-emergency-alerts-to-iphone-5-and-4s-with-software-update>, about 10 or 20 seconds after I open or switch to the page. Maybe caused by an add ? bp-f9c14d3e-724f-4ac1-ac9e-729582130615
(In reply to Jo Hermans from comment #9) > Right at this moment, I'm hitting the bug at > <http://appleinsider.com/articles/13/06/14/att-to-add-emergency-alerts-to- > iphone-5-and-4s-with-software-update>, about 10 or 20 seconds after I open > or switch to the page. Maybe caused by an add ? > > bp-f9c14d3e-724f-4ac1-ac9e-729582130615
Summary: crash in js::PCToLineNumber → crash in addProfileEntry @ js::PCToLineNumber
(In reply to Jo Hermans from comment #9) Filed bug 883560.
Blocks: 1329181

Reopening bug since there are crash reports in the last 6 months.

Status: REOPENED → RESOLVED
Closed: 12 years ago → 3 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Whiteboard: qa-not-actionable
Severity: critical → S3
Priority: -- → P3
Crash Signature: [@ js::PCToLineNumber(unsigned int, unsigned char*, unsigned char*, unsigned char*, unsigned int*)] [@ js::PCToLineNumber] → [@ js::PCToLineNumber] [@ js::PCToLineNumber]
You need to log in before you can comment on or make changes to this bug.