327299 - valgrind reports leaks on startup

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[wbrana]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060214 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060214 Firefox/1.5

valgrind 3.1 reports leaks on startup

Reproducible: Always

Steps to Reproduce:
1. run valgrind --leak-check=full --show-reachable=yes firefox-bin
2.
3.

Comment 1

[wbrana]

Attachment: valgrind output

Comment 2

[Philip Withnall (unavailable)]

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060215 Firefox/1.6a1
I'm not getting any memory leaks, just some warnings about jmps and movs based on uninitialised values.

Comment 3

[Philip Withnall (unavailable)]

Attachment: Non-leaking valgrind output.

If you can reproduce this with the latest version of Firefox, please re-open this bug report. Otherwise, I'll consider this invalid (see attachment).

Comment 4

[wbrana]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060218 Firefox/1.6a1

==10509== ERROR SUMMARY: 113 errors from 10 contexts (suppressed: 202 from 1)
==10509== malloc/free: in use at exit: 1,190,832 bytes in 12,992 blocks.
==10509== malloc/free: 213,269 allocs, 200,277 frees, 56,971,232 bytes allocated.
==10509== For counts of detected errors, rerun with: -v
==10509== searching for pointers to 12,992 not-freed blocks.
==10509== checked 27,845,876 bytes.

==10512== ERROR SUMMARY: 6 errors from 3 contexts (suppressed: 140 from 1)
==10512== malloc/free: in use at exit: 1,629,373 bytes in 15,892 blocks.
==10512== malloc/free: 31,769 allocs, 15,877 frees, 12,591,198 bytes allocated.
==10512== For counts of detected errors, rerun with: -v
==10512== searching for pointers to 15,892 not-freed blocks.
==10512== checked 19,280,380 bytes.

Comment 5

[Hermann Schwab]

(In reply to comment #4)
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060218 Firefox/1.6a1

You've used the latest version, but what about the profile?
Do you see these leaks also in safe-mode, or starting with a pristine profile?
Do you have extensions installed?

Comment 6

[Philip Withnall (unavailable)]

Could you also re-run valgrind with the -v option in addition to the other options you were using?

Comment 7

[Ryan VanderMeulen [:RyanVM]]

Is this still happening on the current trunk or 3.0 beta builds?

Comment 8

[lexual]

Feedback timeout.