Closed
Bug 938310
Opened 11 years ago
Closed 6 years ago
Shadereditor tests use a lot of memory
Categories
(DevTools Graveyard :: WebGL Shader Editor, defect)
DevTools Graveyard
WebGL Shader Editor
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mccr8, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
4.28 KB,
text/plain
|
Details |
shu looked at memory usage in the Mochitests BC tests, and the shader editor tests seem to use quite a bit of memory, peaking at almost 1.4 gigs of RSS on Linux64. This may not be the cause of the memory problems causing the closure, but it seems related. It would be good if somebody who understood these tests or WebGL investigated if there's something that could be improved here. The attachment contains the RSS after each tests. shu took a complete about:memory log at each point, so he should be able to get you a more detailed breakdown if that is useful, though I think for many of these a large segment of it is heap-unclassified.
Reporter | ||
Comment 3•11 years ago
|
||
Disabling these tests helped the peak RSS quite a bit, but maybe only slight redunced Win7 debug BC orange. tests enabled: https://tbpl.mozilla.org/?tree=Try&rev=50d39c93fc73 tests disabled: https://tbpl.mozilla.org/?tree=Try&rev=defffd947938
No longer blocks: 937997
Comment 4•11 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #3) Thank you.
Updated•11 years ago
|
Whiteboard: [MemShrink]
Comment 5•6 years ago
|
||
Mass-closing inactive (2 years+) bugs on unmaintained devtools components.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•