-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Firefox console warning: Will-change memory consumption is too high. #4686
Comments
Hi @radumas, we just ran into this issue as well. It seems to be a browser issue that may have been fixed since you posted this issue. Can you test again in the latest version of Firefox (51) and let us know if it still happens? |
Hi @seadour. Went to the same page in |
Thanks for trying. Have you upgraded to Leaflet 1.0.3? If so, is the page somewhere public where we can test it, or can you post a sample as a plunkr/jsfiddle for us? |
I haven't updated yet! But I will do and will let you know if that changes anything. Also the map is ☝️, though it's not particularly simple. |
Sounds good. I get the same error on your page with Firefox 51 for Mac. 🙁 (btw, nice app!) |
I'm not convinced this is actually a Leaflet problem. Leaflet is hinting the browser about modifications it will do to the DOM (transform and opacity transitions), by using the In this case Firefox informs us that it believes its optimizations for The reason you're seeing this problem after upgrading to Leaflet 1.0, is that I haven't profiled Leaflet with and without the I'm closing this for now, since I don't see what Leaflet can do about this, but feel free to add suggestions and we'll consider reopening. |
This "problem" is still active with last version of firefox/leaflet. Is it possible to add a leaflet option to completely disable the will-change hint ? MDN recommends that the property be used as a last resort for existing performance issues rather than ones you anticipate could happen. And, when using it, it's recommended to toggle will-change just before an element or property changes and then toggle it off again shortly after the process is finished. |
@jormun-pluxml you can easily override it with a CSS rule. |
Thanks, that's what i finaly did :) |
Override will-change CSS attribute to fix map page not fully rendering on Firefox. See Leaflet/Leaflet#4686.
Override will-change CSS attribute to fix map page not fully rendering on Firefox. See Leaflet/Leaflet#4686.
Override will-change CSS attribute to fix map page not fully rendering on Firefox. See Leaflet/Leaflet#4686.
Override will-change CSS attribute to fix map page not fully rendering on Firefox. See Leaflet/Leaflet#4686.
Can you please describe how to use
|
i did this : |
It matched this page at time of posting this commment, but note that it has now
box added in https://developer.mozilla.org/en-US/docs/Web/CSS/will-change$compare?locale=en-US&to=1392790&from=1342858 edit |
Just changed to
Leaflet 1.0.0-rc1
in my map app and got the following warning in the console for Firefox 47.0 for Ubuntu 16.04.Will-change memory consumption is too high. Budget limit is the document surface area multiplied by 3 (1535100 px). Occurrences of will-change over the budget will be ignored.
The text was updated successfully, but these errors were encountered: