tracking: leaking autoreleased Obj-C objects

RESOLVED INACTIVE

Status

()

Core
General
RESOLVED INACTIVE
8 years ago
2 days ago

People

(Reporter: Josh Aas, Unassigned)

Tracking

({memory-leak, meta})

Trunk
All
Mac OS X
memory-leak, meta
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
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
(Reporter)

Updated

8 years ago
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?

Updated

8 years ago
Keywords: meta, mlk

Updated

8 years ago
Depends on: 562109

Updated

8 years ago
Depends on: 577599

Updated

8 years ago
Depends on: 601959

Updated

8 years ago
Depends on: 611832

Comment 2

2 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.