Open
Bug 1028456
Opened 10 years ago
Updated 2 years ago
More leaks with _PR_Getfd
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
NEW
People
(Reporter: mccr8, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [MemShrink:P3])
Attachments
(1 file)
1.53 KB,
text/plain
|
Details |
No description provided.
Reporter | ||
Comment 1•10 years ago
|
||
Two more fd-related leaks showed up on the merge from m-c. The bc1 wasn't happening 100% of the time. I landed a new fairly broad suppression of _PR_Getfd for them, as there are a few variants of this that have shown up, and I have no idea what is going on.
Reporter | ||
Comment 2•10 years ago
|
||
We're actually suppressing the _PR_Getfd leaks pretty broadly now, FWIW, because they kept coming up. Though pretty small each time.
Whiteboard: [MemShrink]
Updated•10 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P3]
Comment 3•10 years ago
|
||
Just out of curiosity, are LSAN runs --enable-debug or --disable-debug?
Flags: needinfo?(continuation)
Reporter | ||
Comment 4•10 years ago
|
||
Disable. This does cause problems in some areas of the code that don't bother running cleanup code in non-debug builds.
Flags: needinfo?(continuation)
Comment 5•10 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #4) > Disable. This does cause problems in some areas of the code that don't > bother running cleanup code in non-debug builds. Hm. NSPR has some code to recycle its internal file descriptors and comments claim that it is "disabled in opt builds", but reading the code, it looks like that comment is inaccurate. The caching logic looks...confusing. The cache ought to be cleared on shutdown via PR_Cleanup, but I don't think we ever call that...?
Comment 8•8 years ago
|
||
This is still pretty widespread across the mochitest suites.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•