trace_malloc_leaks regression on fxdbug-win32-tb (10.7KB --> 13.8KB)




Bookmarks & History
10 years ago
4 years ago


(Reporter: stevee, Unassigned)


({memory-leak, regression})

Windows XP
memory-leak, regression
Bug Flags:
blocking-firefox3 -
wanted-firefox3 +
wanted1.9.0.x +

Firefox Tracking Flags

(Not tracked)



(1 attachment)



10 years ago

Lk has jumped from ~10.7KB to ~13.8KB on WINNT 5.2 fxdbug-win32-tb Dep Debug + Leak Test.

Build that started 2008/01/17 @ 22:35:00 looks normal.
Build that started 2008/01/17 @ 23:32:25 has increased leak stats.

Looks like it coincides with the landing of bug 382711.
Flags: blocking-firefox3?
Component: General → General
Flags: blocking-firefox3?
Product: Firefox → Core
QA Contact: general → general
Flags: blocking1.9?
Assignee: nobody → dietrich

Comment 1

10 years ago
--> Detrich since bug 382711 is implicated
Flags: blocking1.9? → blocking1.9+
Priority: -- → P1
Assignee: dietrich → nobody
Component: General → Places
Flags: blocking1.9+
Product: Core → Firefox
QA Contact: general → places
Target Milestone: --- → Firefox 3 beta4
Flags: blocking-firefox3?
Flags: blocking-firefox3? → blocking-firefox3+
Assignee: nobody → dietrich
Created attachment 303169 [details] [diff] [review]
backout pre-emptive leak changes from bug 382711

this patch backs out the changes in the patch for bug 382711 that were not related to the bug itself, but were pre-emptive anti-leak changes :p
Attachment #303169 - Flags: review?(sayrer)

Comment 3

10 years ago
does this fix the leak?
i haven't tested on windows yet. on mac, it didn't seem to make a difference, nor did backing out the patch entirely.

Comment 5

10 years ago
The code you are changing shouldn't leak. There should be trace-malloc data in the full log for those builds that will tell you what new objects it thinks are leaking. What are they?
Bloat/Leak Delta Report
Current file:  /e/builds/tinderbox/Fx-Trunk-Memtest/WINNT_5.2_Depend/bloat-cur.log
Previous file: /e/builds/tinderbox/Fx-Trunk-Memtest/WINNT_5.2_Depend/bloat-prev.log

ERROR - unable to calculate bloat/leak data.

^^ Is this the right place, or would new objects be denoted in the "BloatView: ALL (cumulative) LEAK AND BLOAT STATISTICS" table somewhere?

Comment 7

10 years ago
That's the right place. How frustrating!


10 years ago
Priority: P1 → P3
Target Milestone: Firefox 3 beta4 → Firefox 3
Upping this for now.

What is the status here? In comment 4 sounds like backing out bug 382711 doesn't help at all, wouldn't that mean that this is a regression from something else?
Priority: P3 → P2
(In reply to comment #8)
> Upping this for now.
> In comment 4 sounds like backing out bug 382711
> doesn't help at all, 

no, the leak didn't occur on mac, so testing on mac at all is pointless. i'll try to get some time to set up a windows vm to test this, but probably not going to happen for b5.
given that lk is now at 77k, I'm not really thinking we should block on 3.1k right now.  Time to ship is now, but we want to drill down on this as soon as the dust starts to settle a little.
Flags: wanted1.9.0.x+
Flags: wanted-firefox3+
Flags: blocking-firefox3-
Flags: blocking-firefox3+
Target Milestone: Firefox 3 → ---
Attachment #303169 - Flags: review?(sayrer)
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".

In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body   contains   places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.

Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.

Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Assignee: dietrich → nobody
This is no more actionable
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.