Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Memory leak in Octane benchmark #28

Open
rschoen opened this issue Apr 23, 2015 · 0 comments
Open

Memory leak in Octane benchmark #28

rschoen opened this issue Apr 23, 2015 · 0 comments

Comments

@rschoen
Copy link

rschoen commented Apr 23, 2015

Reported by masoomeh.rudafshani, Apr 13, 2015
What steps will reproduce the problem?

  1. Running the pdfjs benchmark iteratively generates the leaked objects.

What is the expected output? What do you see instead?
The attached graphs show the memory graph before and after fixing the leaks. The graph after the fix is expected.

What version of the product are you using? On what operating system?
Octane benchmark, revision 33. The experiments are done on Ubuntu, in Chrome Version 36.0.1985.125

Please provide any additional information below.
The memory leak is caused by not releasing the logs generated during one execution of benchmark. The logs are accumulated and generates the memory leak.

pdfjsbefore

pdfjsafter

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant