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

Memory leak in Octane benchmark #28

@rschoen

Description

@rschoen

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions