Firefox crashes after running several hours

Our application, which is in late stages of development, is causing mozilla Firefox to crash after running several hours.
Looking at the server side with Java Visual VM we see no unusal simptoms.
I wonder if someone can suggest a course of action to find out what is happening.
The report is shown below:

AdapterDeviceID: 0x0166
AdapterVendorID: 0x8086
Add-ons: %7BF003DA68-8256-4b37-A6C4-350FA04494DF%7D:6.5,,%7B25A1388B-6B18-46c3-BEBA-A81915D0DE8F%7D:,%7B82AF8DCA-6DE9-405D-BD5E-43525BDAD38A%7D:,,,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:25.0,
AvailablePageFile: 4116598784
AvailablePhysicalMemory: 205504512
AvailableVirtualMemory: 513236992
BuildID: 20131025151332
CrashTime: 1384392707
EMCheckCompatibility: true
InstallTime: 1383756577
Notes: AdapterVendorID: 0x8086, AdapterDeviceID: 0x0166, AdapterSubsysID: 05841028, AdapterDriverVersion:
D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ 
OOMAllocationSize: 52
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: release
SecondsSinceLastCrash: 72866
StartupTime: 1384378373
SystemMemoryUsePercentage: 97
Theme: classic/1.0
Throttleable: 1
TotalVirtualMemory: 4294836224
URL: https://localhost:8443/Pv3/#!FdDevices/
Vendor: Mozilla
Version: 25.0
Winsock_LSP: MSAFD Tcpip [TCP/IP]
 : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
 : 2 : 2 :  
 : 2 : 3 : %SystemRoot%\system32\mswsock.dll 
 MSAFD Tcpip [TCP/IPv6]
 : 2 : 1 :  
 MSAFD Tcpip [UDP/IPv6]
 : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
 MSAFD Tcpip [RAW/IPv6]
 : 2 : 3 :  
 RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
 RSVP TCP Service Provider : 2 : 1 :  
 RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
 RSVP UDP Service Provider : 2 : 2 :  
 MSAFD RfComm [Bluetooth]
 : 2 : 1 : %SystemRoot%\system32\mswsock.dll

This report also contains technical information about the state of the application when it crashed.

It looks like something is leaking memory on the client side, but hard to say if it is the Vaadin widgetset JS or a browser bug somehow triggered by it.

See what about:memory says and whether the increase in memory usage depends on user actions or not. In the latter case, is server push or polling in use?.
You could check e.g.
the links on this page

The Firefox version is mentioned in the dump above but which Vaadin version are you using? Are you using Vaadin add-ons that might cause problems? How about which browser add-ons are installed/in use?

Using Vaadin 7.1.7.
Some of my tests were done with all Firefox add-ons disabled, with no improvement.
I have several Vaadin add-ons but the part of code causing this (see below) is quite simple.

After running several scenarios I more or less know which part of my code is causing this: a graphical representation of a device that contains many divs, images, etc., and which has a timer-basaed refresher which redisplays the images every 2 minutes. To trigger a faster memory consumption I make it run even faster.
Tested in several other browsers, it has no problems except on firefox.
The about:memory tool shows a large (and growing) size on this area:

  870,217,616 B (69.50%) ā”€ā”€ elements/non-asm.js

It appears I can also reproduce the same on IE10! Of course I will also test other browsers.
Ideally Iā€™d like to find a minimal application that can cause a similar problem.

Also I noticed we use the ContextMenu add-on, I will check if removing it changes the observed pattern

Removing ContextMenu seems to fully stop the memory growth in Google Chrome and IE (but only slowdown the growth on FF).
This is really great news for us, although I need to yet create a more isolated scenario to fully be sure.


thanks for the report. I will attempt to investigate and address the issue as soon as possible. Hopefully during this week.

I just received a temporary fix for the memory leak, a precursor of ContextMenu 4.2.2. I wanted to thank you Peter and Antti for this quick fix.

My initial tests show zero leaks in Chrome, and much slower leaks in Firefox (which is known to have memory leaks all over).


Revision 4.4 released to Directory. Contains the memory leak fix as well as other merged community pull requests. Thanks for all the participants!