Closed
Bug 1235552
Opened 8 years ago
Closed 4 years ago
Automated crash burn test system
Categories
(Testing :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: mikhail.rokhin, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.9) Gecko/201000101 Firefox/99.9 Build ID: 20151223140742 Steps to reproduce: It would be nice, whether you create the series of tests on your side. For e.g. 12 opened pages of youtube and/or other video streaming at 4k resolution to let memory leakage issues develop faster, highly loaded pages like msn, socials (fb, vk.com, twitter.com, etc), looped very complex webgl, etc. running 24/7 (under debugger with memory profiler and without; ran under gdb in my case FF didn't fail and crash, but very slowly so I gave up - may there be issue in FF built-in crash tracer/reporter either?).
Reporter | ||
Updated•8 years ago
|
OS: Unspecified → All
Hardware: Unspecified → All
Like the https://areweslimyet.com/?
Severity: normal → enhancement
Component: Untriaged → General
Product: Firefox → Testing
Whiteboard: [MemShrink]
Reporter | ||
Comment 2•8 years ago
|
||
(In reply to YF (Yang) from comment #1) > Like the https://areweslimyet.com/? Happy New Year! Reads good and may be improved)
Updated•8 years ago
|
Whiteboard: [MemShrink]
Updated•4 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•