Closed Bug 41871 Opened 24 years ago Closed 24 years ago

CBrowserContainer's mRefCnt never goes to 0

Categories

(Core Graveyard :: Java APIs to WebShell, defect, P3)

Product:
Core Graveyard
Component:
Java APIs to WebShell
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: edburns, Assigned: edburns)

Details

Attachments

(4 files)

Research document.
4.34 KB, text/plain
Details
Fix for this bug, first iteration.
2.17 KB, patch
Details | Diff | Splinter Review
Fix for this bug, first iteration, Unified diff.
3.07 KB, patch
Details | Diff | Splinter Review
Research document, with comments.
5.33 KB, text/plain
Details 
DocumentLoadListenerImpl mRefCnt never goes to 0
I filed, I accept
Status: NEW → ASSIGNED
Changed Summary.  DocumentLoadListener is no longer in webclient.
Summary: DocumentLoadListenerImpl mRefCnt never goes to 0 → CBrowserContainer's mRefCnt never goes to 0
Attached file Research document. — 

    
    

    
  


  

    
    

    
  
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: 24 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: