Firefox Nightly 11/12/12 32bit and 64bit javascript leak

RESOLVED INCOMPLETE

Status

()

Core
JavaScript Engine
RESOLVED INCOMPLETE
5 years ago
2 years ago

People

(Reporter: yipeskop, Unassigned)

Tracking

Trunk
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 680795 [details]
sunspider results.txt

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:19.0) Gecko/19.0 Firefox/19.0
Build ID: 20121112030753

Steps to reproduce:

I did a series of repeated benchmark tests using sunspider-0.9.1 without closing the browser between each test.


Actual results:

The browser took an increasing amount of time to complete each test. By the 11th iteration, the browser took twice as long to finish the benchmark as it did when it first started.


Expected results:

The time required to complete each test should have remained pretty constant.
I don't understand why do you mention "leak" in the summary while there is nothing memory related in the comment.

Please provide a testcase or a public URL for that benchmark test.
Assignee: nobody → general
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Whiteboard: [js:waitingforinfo]

Updated

5 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Keywords: testcase-wanted
Resolution: --- → INCOMPLETE
Whiteboard: [js:waitingforinfo]
Keywords: testcase-wanted
You need to log in before you can comment on or make changes to this bug.