[@ mozalloc_handle_oom | nsCSSCompressedDataBlock::Clone]

RESOLVED INCOMPLETE

Status

()

Core
CSS Parsing and Computation
--
critical
RESOLVED INCOMPLETE
8 years ago
2 months ago

People

(Reporter: timeless, Unassigned)

Tracking

({crash})

Trunk
x86
Windows XP
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

8 years ago
attachment 442967 [details]

ChildEBP RetAddr  
0012c78c 7c91de7a ntdll!KiFastSystemCallRet
0012c790 7c81cace ntdll!NtTerminateProcess+0xc
0012c88c 7c81cb26 kernel32!_ExitProcess+0x62
0012c8a0 7813179e kernel32!ExitProcess+0x14
0012c8ac 78131b66 MOZCRT19!__crtExitProcess
0012c8e4 78131c0e MOZCRT19!doexit
0012c8f4 7813d9ed MOZCRT19!_exit
0012c940 005f19f2 MOZCRT19!raise
0012c960 005f1a2a mozalloc!mozalloc_abort
0012c968 102488f7 mozalloc!mozalloc_handle_oom
0012c98c 101c8150 xul!nsCSSCompressedDataBlock::Clone(void)+0x23 [e:\builds\moz2_slave\mozilla-central-win32-nightly\build\layout\style\nscssdatablock.cpp @ 433]
0012c9a0 10023aec xul!nsCSSDeclaration::EnsureMutable(void)+0x29 [e:\builds\moz2_slave\mozilla-central-win32-nightly\build\layout\style\nscssdeclaration.cpp @ 1325]

Do we intend to do something about such crashes?
What did you do to cause this crash?  And how is it related to bug 561469?

Comment 2

8 years ago
The other bug is with OOPP enabled and this one is with OOPP disabled and that is the only difference. 

I don't know why they seem to point to different causes for the crash. In either case the browser eats up more and more memory and eventually crashes. The cause for the high memory consumption is the Lord of Ultima game but on IE8 it seems to stabilize at a certain point or gets released again regularly but on Minefield it just keeps on consuming more and more of it.
(Assignee)

Updated

7 years ago
Crash Signature: [@ mozalloc_handle_oom | nsCSSCompressedDataBlock::Clone]
nsCSSCompressedDataBlock is gone so it's not worth tracking these signatures anymore.
Please file new bugs as appropriate.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.