Open
Bug 1400237
(GCCrashes)
Opened 7 years ago
Updated 20 days ago
[meta] GC crashes
Categories
(Core :: JavaScript: GC, task, P2)
Tracking
()
NEW
People
(Reporter: jonco, Unassigned)
References
(Depends on 45 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
Meta bug to collect ongoing crashes during GC.
Updated•7 years ago
|
Alias: GCCrashes
Comment 1•7 years ago
|
||
P2, athough individual bugs that affect many users should have a higher priority.
Priority: -- → P2
Comment 2•7 years ago
|
||
Jon, the bug still causes crashes: https://crash-stats.mozilla.com/report/index/278ac344-db16-401e-901a-2ca830171023 I have chosen in the settings to produce detailed crash reports, so can you please look at it to see why garbage can not get properly collected without this crash? Otherwise this bug is not reproducible. To me it has happened when I was watching a YouTube video (in a mature session). Thank you in advance.
Flags: needinfo?(jcoppeard)
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to User Dderss from comment #2) This is the same crash as bug 1275172. Unfortunately for this kind of crash it's not possible to determine what the problem is from the crash report. It could be one of several things, e.g. heap corruption, a GC bug, faulty hardware.
Flags: needinfo?(jcoppeard)
Comment 4•7 years ago
|
||
Thanks for reply, Jon. Could you please write a module for FireFox main process that could be turned on by passing of a parameter in the command line so FireFox would automatically make memory snapshots? For example, something like "firefox.exe -memsnapshots"? Maybe with such option available the latest automatically made snapshot saved would help you guys understand what is going on. Prosumers like myself who have interested in finally making the browser stable for heavy use would totally agree to run their browsers with such parameters, even though it would make the work of the browser slower.
Updated•6 years ago
|
Updated•4 years ago
|
Type: enhancement → task
Updated•2 years ago
|
Severity: normal → S3
Updated•3 months ago
|
Updated•20 days ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•