Closed
Bug 9865
Opened 25 years ago
Closed 25 years ago
[malloc] memory allocation problems - xpcom
Categories
(Core Graveyard :: Tracking, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
M15
People
(Reporter: chofmann, Assigned: dp)
References
Details
[malloc] memory allocation problems - xpcom
check bug 8227 for more details on what needs to be done to this code
s:/mozilla/xpcom/ds/nsAtomTable.cpp
Deref-error: "id", line 124
s:/mozilla/xpcom/proxy/src/nsProxyEvent.cpp
Deref-error: "proxyInfo", line 190
s:/mozilla/xpcom/reflect/xptcall/src/md/test/stub_test.cpp
Deref-error: "b", line 180
Deref-error: "b", line 182
s:/mozilla/xpcom/tests/dynamic/TestDynamic.cpp
Deref-error: "factory", line 123
s:/mozilla/xpcom/tests/TestArray.cpp
Deref-error: "foo", line 102
Deref-error: "foo", line 104
s:/mozilla/xpcom/tests/TestBuffers.cpp
Deref-error: "reader", line 144
Deref-error: "reader", line 155
s:/mozilla/xpcom/tests/TestCOMPtr.cpp
Deref-error: "foop", line 181
Deref-error: "barp", line 273
Deref-error: "raw_foo1p", line 516
Deref-error: "raw_foo2p", line 519
s:/mozilla/xpcom/tests/TestObserverService.cpp
Deref-error: "aObserver", line 87
Deref-error: "bObserver", line 89
s:/mozilla/xpcom/tests/TestServMgr.cpp
Deref-error: "listener", line 129
Deref-error: "listener", line 137
Deref-error: "listener", line 154
Deref-error: "listener", line 174
s:/mozilla/xpcom/tests/windows/TestCOM.cpp
Deref-error: "inst", line 134
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M11
Assignee | ||
Updated•25 years ago
|
Whiteboard: [HELP WANTED]
Assignee | ||
Updated•25 years ago
|
Whiteboard: [HELP WANTED]
Target Milestone: M11 → M15
Assignee | ||
Comment 1•25 years ago
|
||
Technically this can happen post beta since most of the files in question are in
test/ anyway. Only one file ds/nsAtomTable.cpp needs the fix.
Assignee | ||
Comment 2•25 years ago
|
||
These are fine now.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•