Closed
Bug 1312910
Opened 9 years ago
Closed 9 years ago
Huge slop and large unreported data with DMD at sci.esa.int/where_is_rosetta/
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: lolo2bdx, Unassigned)
Details
(Whiteboard: [MemShrink])
Attachments
(1 file)
|
9.14 MB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20161019084923
Steps to reproduce:
1) On Ubuntu 16.04 (64-bit PC), with dmd enabled, build and launch firefox
2) In a first tab, open the following link : http://sci.esa.int/where_is_rosetta/
3) Click on "play" when available
4) In a second tab, open about:memory and launch a measurement
=> The measurement gives a lot of slop in class(Object)/objects in the js compartment of http://sci.esa.int/where_is_rosetta/
5) Save DMD output and analyse this report
Actual results:
There is a lot of unreported data in the DMD report (here : 32.08% of unreported data)
Expected results:
Some data should be unreported in the DMD report, but not that much.
Comment 1•9 years ago
|
||
It looks like most of this heap-unclassified stems from mozilla::DoTexImage().
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
Comment 2•9 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #1)
> It looks like most of this heap-unclassified stems from
> mozilla::DoTexImage().
That function, and various other texture-related functions. They all end up going through nouveau_drm_screen_create().
Unfortunately gfx memory like this is impossible to measure in a way that will satisfy DMD, because the malloc calls occur within the gfx driver which we have no control over. (I wrote about the difficulty of this at https://blog.mozilla.org/nnethercote/2014/07/07/measuring-memory-used-by-third-party-code/.)
So I don't think there is anything we can do here, alas.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(n.nethercote)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•