Closed Bug 714643 Opened 13 years ago Closed 13 years ago

Crash report page leaking - consuming memory

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jmjjeffery, Unassigned)

References

(
URL
)

Details

(Keywords: regression)

Attachments

(3 files)

about:memory
143.50 KB, text/plain
Details
New about memory update
166.89 KB, text/plain
Details
edge log file
3.87 MB, text/plain
Details 
Visit this page and check in the TaskManager of Win7 x64 bit with latest hourly build of win32 and you should see memory being consumed rapidly.

https://crash-stats.mozilla.com/report/list?signature=nsDownload%3A%3AUpdateDB%28%29
Haven't managed to reproduce on linux. No shutdown leaks, no huge memory usage increase.
Jim, is this is a clean profile?  It's possible extensions are involved here.
WFM on Win7 x64 and current tip.
Attached file about:memory — 

    
    

    
  
Got it to do it again this morning...

Visit URL (mid click to get a new tab)
I then clicked Signature Summary 
Checked Taskmanager and it was taking off eating RAM




I killed the tab before the browser had a chance to crash - 

It seems intermittent - I could trigger it again trying to find the exact STR, but at the moment I can't..

This is an older profile, but I only have two addons- Flashblock & Console2, as I tester/button pusher I feel its best to test in as pure a form as possible.

This test was done using cset: https://hg.mozilla.org/mozilla-central/rev/cb73188eedf8 m-c hourly build on win7 x64


added attachment - about:memory verbose

    
    

    
  
Crud, I just looked at my attachment and its not showing the massive memory use for heap-unclassified, GC/CC must of cleared before I could grab it with copy/paste.  

This is very intermittent and I'm beginning to think its a timing issue.

I'll try and grab about:memory again, if I can get it to repo...

    
    

    
  
If you can reproduce it and GG/CC doesn't immediately collect everything, could you
create a CC log https://wiki.mozilla.org/Performance:Leak_Tools#Cycle_collector_heap_dump
I'd prefer the script from the 3rd gray box.

    
    

    
  


  
It seems to create log \cc-edges-1.3660.log , but I'm not finding the file anywhere on the drive.  I manually looked in Windows/temp and the user temp (local) on win7, x64 and not finding the file.

New updated about:memory - verbose

    
    

    
  
Please please try to find the regression range.

    
    

    
  

      
      
      
      

        Attached file
          
        edge log file
        — 
      

    


  
OK, got this to work, but despite the instuctions on the performanceleak page, I had to run the Nighly as Administrator - and I am indeed using the very latest Nightly m-c win32 build (hourly).  

File was located on the Main drive, in my setup drive J:

Hope this helps.

    
    

    
  
Ehsan did you break the CC dumper?

    
    

    
  
He fixed it :)

    
    

    
  
Well why is he getting the dump in a totally random location then?

    
    

    
  
That is what Windows gives as temp dir, I guess.

Anyway, there is some large js object graph, but that doesn't explain the 
834,897,574 B (89.28%) -- heap-unclassified

    
    

    
  
Actually, the large graph is just whatever is alive, XBL, some XUL stuff etc. I think.

You're saying that you can close the tab when it is eating more and more memory?
Then it is not cycle collector itself taking that memory.

Could you perhaps run some profiler to see what is taking the CPU time?

    
    

    
  
(In reply to Olli Pettay [:smaug] from comment #15)
> Actually, the large graph is just whatever is alive, XBL, some XUL stuff
> etc. I think.
> 
> You're saying that you can close the tab when it is eating more and more
> memory?
> Then it is not cycle collector itself taking that memory.
> 
> Could you perhaps run some profiler to see what is taking the CPU time?

Sorry, but now your getting over my head..  I don't know how or what to do - sorry.

    
    

    
  
I have not been able to repo this in 2 days now.  Unless someone has any idea, I'm going to close this as WFM.

    
    

    
  
Still cannot repo - closing
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: