OOM | small while memory is available
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: kami911, Unassigned)
Details
I got these reports from one of users. Do you have idea what causes this?
https://crash-stats.mozilla.org/report/index/3d759b2d-f818-443f-b995-561ec0220210
https://crash-stats.mozilla.org/report/index/d596b4a9-8cc4-498e-977c-f02d40220210
https://crash-stats.mozilla.org/report/index/3bcce90b-d27c-402c-b31a-e0dcc0220210
https://crash-stats.mozilla.org/report/index/6ad9dad9-0447-42da-8aeb-7009a0220210
https://crash-stats.mozilla.org/report/index/b3a89a24-af6f-473c-a754-fa0d00220210
Comment 1•3 years ago
|
||
Seems like quite a few bugs with this signature, maybe duplicate after bug 1673778 ?
Comment 2•3 years ago
•
|
||
Crash reports say:
MOZ_CRASH Reason (Raw) [unhandlable oom] Failed to allocate slots while tenuring.
With a free VM size of ~190M, which seems small. I suspect this is a 32-bit build that's browsing heavy websites and eventually crashes due to memory fragmentation (the machine has 3GB, so we're also losing 1GB of RAM from the actual hardware due to being 32-bit).
It's also on Windows 7 running 2009-era video drivers.
Not sure there's anything really actionable here.
Updated•3 years ago
|
Description
•