Open Bug 559073 Opened 14 years ago Updated 2 years ago

[meta] tracking: leaking autoreleased Obj-C objects

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
All
macOS
Type:
defect

Tracking

()

People

(Reporter: jaas, Unassigned)

References

(Depends on 2 open bugs)

Details

(Keywords: memory-leak, meta) 

We have a number of known cases where we leak autoreleased Obj-C objects. These will be fixed in multiple bugs which can be tracked here.

Typically these leaks cause the following type of output:

2010-04-13 10:49:28.025 firefox-bin[78216:a0f] *** __NSAutoreleaseNoPool(): Object 0x401e4b0 of class NSFont autoreleased with no pool in place - just leaking
Depends on: 559075
Depends on: 559180
Depends on: 559400
Since it seems like the current deps here have been resolved (bug  	    338041 seems to be WFM, and the goal of bug 338645 has probably been accomplished by the other deps here), would it be worthwhile to get something added to the tinderbox logparsers to flag/go orange on new instances of autorelease leaks when people try-build and check in?
Keywords: meta, mlk
Depends on: 562109
Depends on: 577599
Depends on: 601959
Depends on: 611832
Severity: normal → S3
Summary: tracking: leaking autoreleased Obj-C objects → [meta] tracking: leaking autoreleased Obj-C objects
You need to log in before you can comment on or make changes to this bug.