Closed Bug 1384854 Opened 7 years ago Closed 7 years ago

Stylo: Crash in alloc::oom::oom

Categories

(Core :: CSS Parsing and Computation, defect, P1)

56 Branch
Unspecified
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1383981
Tracking Status
firefox-esr52 --- unaffected
firefox54 --- unaffected
firefox55 --- unaffected
firefox56 --- affected

People

(Reporter: calixte, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-0625be8a-e875-4e76-85aa-bf53b0170726.
=============================================================

There are 2 crashes in nightly 56.
Priority: -- → P2
OOM in StyleBuilder::build on a 64bit platform? Do we allocate a lot in that function?

I don't quite understand how this can happen...
Me neither, build allocates a single style context, and an Arc, as far as I can tell...
I can simply reproduce the OOM from this site: http://www.robohornet.org/#et=css_selectors

STR:
1. Click the RUN button on the top right side.
2. The test runner window appears and scroll down the list.
3. Tab frozen and go to watch memory usage, e.g. macOS Activity monitor/Memory.
4. Memory usage growing until OOM.
Priority: P2 → P1
(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #4)
> That is bug 1383981.

Yes, for other cases, they are about MP4 demuxer. I think we can dupe this bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.