Closed Bug 1361016 Opened 7 years ago Closed 7 years ago

Destroying the worker causes the virtual address space to leak, which sooner or later leads to a Firefox crash

Categories

(Core :: DOM: Workers, defect, P2)

Product:
Core
Component:
DOM: Workers
Version:
53 Branch
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1377738

People

(Reporter: CoolCmd, Assigned: baku)

Details

(Whiteboard: [MemShrink:P1])

Attachments

(2 files)

coolcmd.html
911 bytes, text/html
Details
coolcmd.png
91.97 KB, image/png
Details
Attached file coolcmd.html — 
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170413192749

Steps to reproduce:

Run attached coolcmd.html.
Open the "Process Explorer" utility (https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx), open properties of the Firefox's content process, watch for "Virtual Size" parameter.


Actual results:

"Virtual Size" is unconditionally grows.
See the attached coolcmd.png. Red graph - working set, brown - virtual size.


Expected results:

"Virtual Size" should not unconditionally grow.
Attached image coolcmd.png — 
Component: Untriaged → DOM: Workers
Product: Firefox → Core

    
  
Summary: Destroying the worker causes the virtual space to leak, which sooner or later leads to a Firefox crash → Destroying the worker causes the virtual address space to leak, which sooner or later leads to a Firefox crash
Whiteboard: [MemShrink]

    
  
Whiteboard: [MemShrink] → [MemShrink:P1]

    
    

    
  
baku, can you take a look here, please?
Flags: needinfo?(amarchesini)
Priority: -- → P2

    
  
Assignee: nobody → amarchesini
Flags: needinfo?(amarchesini)

    
    

    
  
CoolCMD, can you reproduce this in latest nightly after bug 1377738 was fixed

    
    

    
  
(In reply to Danial Horton from comment #3)
> CoolCMD, can you reproduce this in latest nightly after bug 1377738 was fixed

Nightly 56.0a1 Build ID 20170719030206
I can not reproduce my bug. Most likely it is fixed, possibly in bug 1377738.

    
    

    
  
Going to go ahead and dupe this based on comment 4.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: