714690 - Leak of 18 bytes in malloc_zone_malloc as detected by Valgrind on Mac OS X Lion

Status: RESOLVED WONTFIX

(Core :: JavaScript Engine, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Attachment: stack

quit()

shows the attached leak signature on 32-bit debug js shell on m-c changeset d77b056ed4bd on Mac OS X Lion.

CLI command: valgrind --dsymutil=yes --leak-check=full ./js

Using Valgrind SVN rev 12325:

Last Changed Author: florian
Last Changed Rev: 12325
Last Changed Date: 2012-01-02 08:12:30 -0800 (Mon, 02 Jan 2012)

Configured using:

sh ./configure --target=i386-apple-darwin8.0.0 --enable-optimize --disable-debug --enable-profiling --enable-valgrind --disable-tests --enable-type-inference --enable-more-deterministic

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Just to confirm, the error also shows with js opt shells.

Comment 2

[Julian Seward [:jseward]]

Well, that seems like a leak in the system libraries, no?  I bet you
can't repro this on Linux.

Comment 3

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Filed in ADC id 10652055. Will the lack of Spidermonkey lines be a clue in deciding that this is a problem with the system libraries?

Comment 4

[Julian Seward [:jseward]]

Uh, as per comment #2, did you check whether you can repro this leak on Linux?

Comment 5

[Nicholas Nethercote [inactive]]

It won't reproduce on Linux, because Linux doesn't have malloc_zone_malloc and the libraries are all Mac-specific.  A deeper stack-trace (via --num-callers=50) might be instructive.

Comment 6

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Attachment: Valgrind stack w/ --num-callers=50

Comment 7

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

> Uh, as per comment #2, did you check whether you can repro this leak on
> Linux?

Yes, I did, it does not reproduce on 64-bit opt shell w/ Valgrind.

Comment 8

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

> Yes, I did, it does not reproduce on 64-bit opt shell w/ Valgrind.

*does not reproduce on Linux*

Comment 9

[Nicholas Nethercote [inactive]]

I thought I commented on this... maybe the comment was eaten, or maybe I commented in another similar bug.  Anyway, that stack trace is all Mac system library stuff beyond our control.