Memory leak?

[mattdesl]

I am testing on a new MacBook Pro and seeing a lot of "Out of Memory" system errors after 100-200 consecutive reloads in a very heavy WebGL scene (loading 3D models and procedural geometry).

It's hard to know whether the memory leak is in Chrome, or budo, or somewhere else, but I'll start digging to see what's up. Generally the memory problem goes away as soon as I quit Chrome, but in some cases I've seen the memory come back as soon as I terminate the budo process.

Would be interested to hear if anybody else has run into this.

[arturitu]

To me it has not happened and I usually work with Chrome and Budo, but perhaps if because they aren't very heavy WebGL scenes

[monfera]

Seemingly unrelated problem: may well not be budo specific (as budo relies on browserify). It happens with Firefox only - Chrome, Safari are fine, also using a MBP. Even on first load, with no WebGL content at all, large projects, in this case, plotly.js cause lots of source map loading in FF such that FF hits 20GB memory use in about a minute or two. It descends into all node_modules. Already happens on the first load. Problem goes away completely with the budo --no-debug option. Just asking in case you saw it before, otherwise will investigate as it seems unrelated.

[mattdesl]

Problem goes away completely with the budo --no-debug option

I have a feeling this might not be a budo issue, but rather a browser issue. I've experienced a lot of sluggish-ness with browsers in the past when handling large bundles with many source maps. Removing source maps with --no-debug pretty much always solves the problem.

Not sure how to go about this one, to be honest!