Closed Bug 781680 Opened 8 years ago Closed 8 years ago

IonMonkey: Track IonCode in MemoryMetrics

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: sstangl, Unassigned)

References

Details

(Whiteboard: [ion:p1])

Attachments

(2 files)

Attached file Backtrace.
Failure in MemoryMetrics.cpp on x86_64 Debug IonMonkey browser. Might involve DOM natives.

Appears to be trivially reproducible by visiting dromaeo.com. It sometimes triggers before you get a chance to hit "Run". Also occasionally reproducible by conducting a Google search.

Built with HG commit 8c33b71cce49 (Thu Aug 09 19:43:47 2012 +0200).

Backtrace attached.
Attached patch patchSplinter Review
Fixes the issue without creating an additional tracking kind in cStats. Traking IonCode as part of the Script seems reasonable.

As far as I can tell, this fixes the assertion. I managed to run Dromaeo about halfway (before successfully stopping it) several times, and Google searches didn't assert.
Attachment #650739 - Flags: review?(dvander)
Summary: IonMonkey: Assertion Failure: n2 % gc::ArenaSize == 0 in MemoryMetrics.cpp:60 → IonMonkey: Track IonCode in MemoryMetrics
Attachment #650739 - Flags: review?(dvander) → review+
http://hg.mozilla.org/projects/ionmonkey/rev/b3ece996df7e
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.