Open Bug 1089614 Opened 10 years ago Updated 2 years ago

logalloc causes a deadlock on shutdown

Categories

(Core :: Memory Allocator, defect)

x86_64
macOS
defect

Tracking

()

People

(Reporter: ggp, Unassigned)

References

Details

Attachments

(1 file)

Attached file stack
When logalloc is being used to record memory allocations and XPCOM is being shutdown, the write() call made by FdPrintf causes malloc() to be called. But we are, of course, already inside replace_malloc(), and re-entering causes it to attempt to lock an already locked sLock. This makes the browser hang on shutdown.

I have reproduced this on Mac (stack attached), but it might also happen in other platforms. Maybe.
This looks like a rather similar, but Mac-specific, variant of bug 1087245. The Mac-specific part comes from the fact that the stack is different, but the general problem -- PoisonIOInterposer allocating memory -- is the same.
Blocks: 1083686
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: