Open
Bug 1236437
Opened 10 years ago
Updated 3 years ago
Leaving Firefox running during a long time exhausts all my file descriptors
Categories
(Core :: Networking, defect, P3)
Core
Networking
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox46 | --- | affected |
People
(Reporter: julienw, Unassigned)
Details
(Whiteboard: [necko-backlog])
Attachments
(1 file)
1.79 MB,
application/gzip
|
Details |
I left my Firefox instances open during my 2-week holiday.
When I came back, I found that nothing was working on my computer. After some debugging I found that the file descriptor space was exhausted.
A quick look at `lsof` showed me that all Firefox instances were exhausting the space.
My aurora instance (the main one, with some hundreds tabs open, e10s with processCount set to 8) had 30K+ open fds. That's for the main process only.
Moreover its Web subprocesses also had between 5K and 11K additional open fds.
So this only instance had 93838 open fds.
So we could say that I shouldn't have changed "dom.ipc.processCount".
However my separate nightly instance I use as Gaia test runner (not e10s) had 15K+ open fds.
Reporter | ||
Comment 1•10 years ago
|
||
Pid 11379 is my not-e10s nightly instance.
All other pids are from my e10s aurora instance.
Updated•10 years ago
|
Component: General → Networking
Product: Firefox → Core
Updated•9 years ago
|
Whiteboard: [necko-backlog]
Comment 2•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 3•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Comment 4•7 years ago
|
||
I found this bug while entering a new bug that happens to have similar keywords.
The lsof output appears to list each thread separately, which is going to massively inflate any count of anything over the real value. Also, the lines with "mem" or "DEL" or anything that doesn't start with a number in the "FD" column aren't file descriptors; they're memory mappings (or other non-fd references, like cwd and rtd), and they don't count against fd limits.
Filtering all that out, it looks about the same as what I see locally in the present day: the parent process has 200-300 fds open, and each child process has a few dozen. Nothing that should run an entire system out of fds in any case — the total number of fds in the attached file is 640.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•