1040592 - Memory leakage related to deadlock detector

Status: RESOLVED DUPLICATE of bug 1027921

(Core :: XPCOM, defect)

Description

[Shian-Yow Wu [:swu]]

+++ This bug was initially created as a clone of Bug #1039914 +++

When doing the interations of array buffer transfer in mochitest of bug 1037358, the "heap-unclassified" in about:memory keeps increasing, it indicates a potential memory leakage.

In the DMD log, there are many unreported heap records related to mozilla::dom::workers::WorkerPrivate::CreateNewSyncLoop().

Comment 1

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Can you attach the DMD log?

Comment 2

[Shian-Yow Wu [:swu]]

Attachment: DMD report

Attached is the DMD report.

Comment 3

[Shian-Yow Wu [:swu]]

Attachment: Test case to reproduce

Attached is the test to reproduce.

Comment 4

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

So this memory is being used in the deadlock detector.  You can see some other things consuming far more than workers, like the cache.  Every time we create a Mutex we put an entry in some hashtable.  It's not clear to me that we ever remove those ...

Comment 5

[Nathan Froyd [:froydnj]]

(In reply to Kyle Huey [:khuey] ([e-mail]) from comment #4)
> So this memory is being used in the deadlock detector.  You can see some
> other things consuming far more than workers, like the cache.  Every time we
> create a Mutex we put an entry in some hashtable.  It's not clear to me that
> we ever remove those ...

Eric had (re)discovered this and was grousing about it at some point...

Comment 6

[Eric Rahm [:erahm]]

See bug 1027921.

Comment 8

[Shian-Yow Wu [:swu]]

(In reply to Eric Rahm [:erahm] from comment #6)
> See bug 1027921.

Thanks for this info.