"uncaught exception: out of memory" error after updating

UNCONFIRMED
Unassigned

Status

()

Core
JavaScript Engine
P3
normal
UNCONFIRMED
a year ago
10 months ago

People

(Reporter: Robo, Unassigned)

Tracking

({triage-deferred})

51 Branch
triage-deferred
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8843212 [details]
unified-memory-report-due-to-JS-OOM-8340.json.gz

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce:

Some time ago we see out of memory errors in log files on our servers. All errors refers to FF v51.
The page uses jQuery and KnocjoutJs libraries.
The error appears when page is loaded and leaved for a long time (hours) without any actions on it.
Issue appears on completely different computers.


Actual results:

JS error in console:
message: uncaught exception: out of memory
line: 0
column: 0
scriptUrl:
userAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

See also memory dump attached


Expected results:

There should be no OOM error.

Updated

a year ago
Component: Untriaged → Untriaged
Product: Firefox → Core

Updated

a year ago
Component: Untriaged → JavaScript Engine

Comment 1

a year ago
We are also seeing lots of OOM reports in our server log files since the public release of FF 52.
OOM errors are thrown at various JS code locations and only FF 52 clients are affected.
More interestingly, almost every faulty client is running on a 32-bit Windows OS (no WOW64/Win64/x64 tag in the useragent string), while 70% of our users have 64-bit Windows.
I've checked older logs and found a few entries like the one above (32-bit FF 51 on 64-bit Windows).

Bug 1343234 might be related, as the most memory in use is classified as "js-non-window"
Keywords: triage-deferred
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.