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

Memory leak when updating from geojson at 15Hz in 3d mode #5662

Open
HeavenlyHost opened this issue Jul 20, 2017 · 3 comments
Open

Memory leak when updating from geojson at 15Hz in 3d mode #5662

HeavenlyHost opened this issue Jul 20, 2017 · 3 comments

Comments

@HeavenlyHost
Copy link

HeavenlyHost commented Jul 20, 2017

Firstly please accept my apologies as this references a problem raised against another project, but the devs on this have suggested that I make you aware of a memory leak within Cesium under my particular scenario.

So our project makes use of Openlayers and ol-cesium, the project updates 2000 points from a geojson object at 15Hz. This data is supplied over a websocket.

Everytime the vector data is updated the vector source is cleared and the geojson is reloaded. The problem is that the ol-cesium (or the cesium library) is not releasing the resources on a source clear and hence can consume considerable amounts of memory very quickly.

The devs from openlayers are unsure at the moment but have suggested that you need to be made aware of this problem.

Are you having memory leak issues at the moment or should I ping this back to them ???

As a workaround I am dropping the layer and recreating it from scratch but this results in a significant flicker within the cesium map, any ideas ???

For your reference see the following... here

@hpinkos
Copy link
Contributor

hpinkos commented Jul 20, 2017

Thanks @HeavenlyHost! We've had a few other users report memory issues. Would you be able to put together a Sandcastle demo that reproduces the issue? That will make it a lot easier for us to track down what's going on. Thanks!

@mramato
Copy link
Contributor

mramato commented Jul 20, 2017

@HeavenlyHost for the blinking you mention in the linked issue, we fixed that with #5632 and it will be out with Cesium 1.36 on August 1st.

I would be surprised if the memory leak you describe is a Cesium issue, it sounds like it could be specific to ol-cesium. As @hpinkos alluded too, please provide a reduced test case that reproduces the issue and we'll be happy to take a look, otherwise there's not much we can do.

This was referenced Dec 1, 2017
@hpinkos
Copy link
Contributor

hpinkos commented Dec 1, 2017

Also reported in #6009 by @newnewplayer and #5774 by @AnotherFoxGuy

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

No branches or pull requests

5 participants