You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
Reported by masoomeh.rudafshani, Apr 13, 2015
What steps will reproduce the problem?
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reported by masoomeh.rudafshani, Apr 13, 2015
What steps will reproduce the problem?
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.
The text was updated successfully, but these errors were encountered: