Skip to content

Dart VM using much more memory than Observatory reports #25592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
azenla opened this issue Jan 27, 2016 · 7 comments
Closed

Dart VM using much more memory than Observatory reports #25592

azenla opened this issue Jan 27, 2016 · 7 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@azenla
Copy link
Contributor

azenla commented Jan 27, 2016

Hello! I have been doing thorough investigations into possible memory leaks in our own codebase for DSA. However, I am noticing that the memory usages displayed in Observatory are massively off from what I am seeing in System Monitoring tools. On the reproduction below, I'm getting hundreds of megabytes more in real memory usage than what I see in Observatory.

I have created a special repository for storing reproductions of these kinds of things. Sorry for not including all the info here, if that is desired rather than externally linking it, please let me know.

Reproduction Information

@Pacane
Copy link

Pacane commented Jan 27, 2016

Nice work

@alexander-doroshko
Copy link

May be related to #25178 and #24613

@floitschG floitschG added the area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. label Jan 27, 2016
@iposva-google
Copy link
Contributor

Not related to #25178 or #24613 as in this report the observatory is not showing where the memory is being consumed unlike in these other issues.

@iposva-google iposva-google added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Jan 28, 2016
@iposva-google iposva-google self-assigned this Jan 28, 2016
@iposva-google
Copy link
Contributor

cc @johnmccutchan @zanderso

@azenla
Copy link
Contributor Author

azenla commented Jan 28, 2016

Has it been reproduced yet? If it is reproduced by others, it could be a potential blocker for 1.14.

@johnmccutchan
Copy link
Contributor

@kaendfinger I have been running your reproduction on Linux with 1.14-dev.7.2 for two hours and I haven't seen anything yet.

Virtual Memory: 705.9 MB
Resident Memory: 175.7 MB
Writable Memory: 169.8 MB

@azenla
Copy link
Contributor Author

azenla commented Jan 28, 2016

@johnmccutchan It looks like this might have been the result of accidentally using the wrong Observatory for another test I was doing, which resulted in the memory usage being higher.

I'm going to close this issue, the memory leak investigation for DSA has lead us to find a leak in our own code. Thanks for the help :)

@azenla azenla closed this as completed Jan 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

6 participants