Closed
Bug 41871
Opened 25 years ago
Closed 25 years ago
CBrowserContainer's mRefCnt never goes to 0
Categories
(Core Graveyard :: Java APIs to WebShell, defect, P3)
Core Graveyard
Java APIs to WebShell
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: edburns, Assigned: edburns)
Details
Attachments
(4 files)
|
4.34 KB,
text/plain
|
Details | |
|
2.17 KB,
patch
|
Details | Diff | Splinter Review | |
|
3.07 KB,
patch
|
Details | Diff | Splinter Review | |
|
5.33 KB,
text/plain
|
Details |
DocumentLoadListenerImpl mRefCnt never goes to 0
Changed Summary. DocumentLoadListener is no longer in webclient.
Summary: DocumentLoadListenerImpl mRefCnt never goes to 0 → CBrowserContainer's mRefCnt never goes to 0
bug=41871
This checkin makes it so CBrowserContainer is properly released. The
problem was that the CBrowserContainer was still registered to the
docShell as a listener. The solution was to call
wcIBrowserContianer::RemoveAllListeners() in the WebShellInitContext
deallocator.
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
||
Updated•14 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•