Closed Bug 1223682 Opened 10 years ago Closed 3 days ago

OOM crashings only just started recently

Categories

(Core :: General, defect)

42 Branch
x86_64
Windows 8.1
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: arch.jslin, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20151029151421 Steps to reproduce: Casually browsing Facebook tab for less than an hour and Firefox resulted in OOM crash (when restarted/resumed from the last crashing, it only used less than 1GB at start, but then it very fast climbed to 2GB and everything started lagging). This symptom only started recently, might be right after I upgraded to 42. I have some screenshots and desc to each screenshot for further info: http://imgur.com/a/NTnfL Actual results: OOM crash Expected results: not OOM crash
OS: Unspecified → Windows 8.1
Hardware: Unspecified → x86_64
Attached file memory report
I can almost feel my firefox is dying yet again, so tried to grab a memory report.
Noticed the super high "heap-unclassified" usage -- 1GB of that stuff dwarfing all the heavy duty sites usages (Facebook, Google+, several Gmail web clients)
Severity: normal → S3

lacks testcase or anything to reproduce

Status: UNCONFIRMED → RESOLVED
Closed: 3 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: