question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Firefox console warning: Will-change memory consumption is too high.

See original GitHub issue

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.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

17reactions
jormun-pluxmlcommented, Mar 26, 2019

i did this : .leaflet-fade-anim .leaflet-tile,.leaflet-zoom-anim .leaflet-zoom-animated { will-change:auto !important; }

13reactions
perliedmancommented, Feb 16, 2017

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 will-change CSS property. No matter what the browser does with this hint, we will use transitions to animate opacity and transform of the tiles.

In this case Firefox informs us that it believes its optimizations for will-change would consume too much memory and ignore it, which is fine.

The reason you’re seeing this problem after upgrading to Leaflet 1.0, is that will-change was not used at all in earlier versions of Leaflet.

I haven’t profiled Leaflet with and without the will-change hint, but my interpretation is that we use it more or less exactly as described here: https://developer.mozilla.org/en/docs/Web/CSS/will-change - the only real alternative would be to rework how transitions are handled altogether - in itself a major refactor - and at least last time we benchmarked, CSS transitions still outperformed transitions implemented in JavaScript.

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

"Will-change memory consumption is too high" firefox issue?
The error simply means that there are too many will-change properties. Read the MDN page, especially the warnings. Now are you using frameworks ......
Read more >
Firefox uses too much memory or CPU resources - How to fix
To determine if an extension or theme is causing Firefox to use too many resources, start Firefox in Troubleshoot Mode and observe its...
Read more >
"Will-change memory consumption is too high" warning on ...
Has anyone else run into this warning message in the console on Firefox? Will-change memory consumption is too high.
Read more >
Will-change Memory Consumption Is Too High. Budget Limit ...
I try to explain it on a other way! On the Firefox there is a warning. Will-change memory consumption is too high. Budget...
Read more >
YouTube Responds Too Slowly on Firefox Sometimes
uBlock Origin could be the source of the 404. The will-change memory consumption issue is arguably pretty generic and is probably related to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found