I'm adding a ?listenerLimit query parameter, which (when assertions are enabled) should be able to help track down common memory leaks. I've run into this many times (I usually hack in code temporarily into TinyEmitter, then remove it), so it will be a very helpful permanent feature for me.
If you set ?listenerLimit=2000, when the 2001st listener is added to ANY TinyEmitter (e.g. Property, etc.), it will error out. It will also console.log incoming maximums, so that you can quickly tell if a leak is likely.
There was a PSA at dev meeting today. @chrisklus and @samreid are out today. Please unassign yourself when you have ready this, and last person feel free to close.
I'm adding a
?listenerLimit
query parameter, which (when assertions are enabled) should be able to help track down common memory leaks. I've run into this many times (I usually hack in code temporarily into TinyEmitter, then remove it), so it will be a very helpful permanent feature for me.If you set
?listenerLimit=2000
, when the 2001st listener is added to ANY TinyEmitter (e.g. Property, etc.), it will error out. It will also console.log incoming maximums, so that you can quickly tell if a leak is likely.Putting on dev board for a PSA.