Skip to content
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

Windows has high memory usage #15572

Open
jonathandturner opened this issue Feb 15, 2017 · 8 comments
Open

Windows has high memory usage #15572

jonathandturner opened this issue Feb 15, 2017 · 8 comments

Comments

@jonathandturner
Copy link

@jonathandturner jonathandturner commented Feb 15, 2017

As mentioned here, here, and here the Windows build is also leaking a fair amount of memory.

This may be related to #15428.

cc @codec-abc, @leeoniya, @BladeMight who mentioned experiencing the issue

@larsbergstrom larsbergstrom mentioned this issue Feb 15, 2017
11 of 11 tasks complete
@jdm jdm added the I-memory-leak label Feb 15, 2017
@codec-abc
Copy link

@codec-abc codec-abc commented Feb 15, 2017

Could you confirm that the link to download the last Windows version for servo is :
https://download.servo.org/nightly/windows-msvc/servo-latest.msi

@leeoniya
Copy link

@leeoniya leeoniya commented Feb 15, 2017

yes this is still an issue. i could not get any site on the start page to display at all. instead servo chews through RAM and has to be process-killed to fully exit.

this is not just a mem-leak, it is basically non-functional on Windows.

@codec-abc
Copy link

@codec-abc codec-abc commented Feb 27, 2017

Tested again today with latest nightly. Seems like the problem is gone.

@jdm
Copy link
Member

@jdm jdm commented Feb 27, 2017

Seems like this can be closed, in that case. Thanks for checking!

@jdm jdm closed this Feb 27, 2017
@jonathandturner
Copy link
Author

@jonathandturner jonathandturner commented Feb 27, 2017

@jdm - this still repros. With last night's nightly, if you click on the link to go to https://medium.com/@dourvaris/my-2015-macbook-pro-retina-exploded-119ea5ea9d1f#.pgd3f8jme from hacker news, you get the same high memory behaviour. It seems to not be as common now, though.

@codec-abc
Copy link

@codec-abc codec-abc commented Feb 27, 2017

My bad for the wrong reporting. I confirm that the issue is still here but is triggered much less frequently than before.

@codec-abc
Copy link

@codec-abc codec-abc commented Mar 13, 2017

I can still reproduce with the nightly and compiling myself servo with MSVC. But the memory leak only happen in release. In debug for the given medium page I am at a stable ~200MB Memory usage.

@jonathandturner
Copy link
Author

@jonathandturner jonathandturner commented Mar 14, 2017

Just a bit of follow-up, to echo what @codec-abc mentioned.

The debug build doesn't finish rendering the page correctly. The image at the top fails to load, showing this:

servo_debug_exploded

Debug mode holds steady between 200 and 300 MB. Memory climbs towards 300 then drops down to 200 or so again.

Release mode is able to render the image in the middle:

servo_release_exploded

But, it quickly begins to consume memory without end.

I attached a debugger and was able to see a little glimpse of what is going on, but would still need to dig in further to see if this is related or just a red herring:

large_mem_usage_servo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.