Closed
Bug 1126986
Opened 6 years ago
Closed 6 years ago
TelemetryFile.jsm compartment uses megabytes of memory!
Categories
(Toolkit :: Telemetry, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1041616
People
(Reporter: vladan, Unassigned)
References
Details
Attachments
(1 file)
|
2.78 KB,
text/plain
|
Details |
I was looking through my about:memory and I noticed TelemetryFile.jsm using anywhere from 1MB to 3.5 MB of memory. The memory is mostly tied up in JS arrays.. objects --> malloc-heap --> elements/non-asm.js I did a quick experiment and found the memory use is normal when there are no files in saved-telemetry-pings directory and memory is use is higher when there are more pings in that directory. The saved ping files themselves are about 100KB each. I suspect we're reading in the saved ping files and somehow inflating their size by a factor of 10.
Comment 1•6 years ago
|
||
See also Bug 1041616. Might be a dupe.
| Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Richard Newman [:rnewman] from comment #1) > See also Bug 1041616. Might be a dupe. Yup I know about that one, I marked it a blocker of this bug when I filed it.
| Reporter | ||
Comment 3•6 years ago
|
||
I investigated and found there is no memory "leak". On startup, Telemetry parses the saved ping files into objects, and they use 4x as much memory as JS objects than in their serialized string from. I'll post a patch soon to only parse the ping files when needed (right before they're sent).
Comment 4•6 years ago
|
||
Sounds like a 100% dupe to me.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1041616
You need to log in
before you can comment on or make changes to this bug.
Description
•