Closed
Bug 985972
Opened 11 years ago
Closed 4 years ago
Memory leak parsing RegExp
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mr.starix, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140314220517
Steps to reproduce:
<HTML>
<HEAD>
<TITLE>Firefox 27.0.1 and Safari 7.0.2 (9537.74.9)</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<SCRIPT type="text/javascript">
var patt1=new RegExp("((.*)(((((((((((((((((((((((((((((((.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}(.*){10}.*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+).*)+))");
document.write(patt1.exec("peace"));
</SCRIPT>
</BODY>
</HTML>
Actual results:
Memory leak and force close in Firefox 28.0
|
Reporter | |
Updated•11 years ago
|
Severity: normal → critical
|
||
Comment 2•11 years ago
|
||
Reproduces in current Nightly. Memory usage jumped to about 2.5GB for the Firefox process and 8GB for the kernel_task process immediately and then slowly grew until I killed the browser at about 15GB of total usage. Attached is a sample of the process from maybe a minute or two into things. Unsurprisingly, all time is spent under Yarr. To find out whether this is a problem with our usage of Yarr or with Yarr itself, I ran the test case in Safari: same results, memory usage exploded and the browser froze. (Oh, I just see the <title> in the test case. Is this reported for webkit, already?) The regexp is pretty hard on all browsers, it seems: Chrome (release and Canary) don't leak memory, but the process in which the test case runs freezes.
Hi reporter,
In order to follow this up, I tried reproducing the reported issue on the latest Firefox Release version 85.0 (64-bit) on a Windows 10 machine but I was unable to see any memory leak.
Since this hasn't had any updates in recent years I'll close it as Resolved WFM. Please feel free to reopen it or open a new bug if you consider it that still occurs.
Regards,
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•