Eric Blade
See also https://github.com/ericblade/quagga2/pull/171
Anyone still having issues with this? I don't believe I've seen it, and I've left quagga open for quite a while on my phone.
@ryanmagits hmm. how old is old? i wonder if it's just something that may not be fixable in older chrome implementations .. might try my fork of the lib, https://github.com/ericblade/quagga2...
You might want to try the "Performance" tab in the Chrome Inspector. I don't see anything obvious and horrible that you're doing there, although i would suspect that if you're...
right, if you're telling it "ideal" is 4kX2k, and whatever you're running on actually has the ability to give you an image that big, you're going to spend a lot...
hmm. not seeing any obvious hotspots in github to really give me an idea of what 'bad' looks like here. i think if you turn on performance capturing while you're...
well, there's a couple of things that i've seen that people have done to cause performance issues before -- one is just running a lot of code inside your onDetected...
set locate: false and define an area, per the readme it does make it faster/less intensive, but does reduce the usability, imo
We should test this, and see if we are leaking by doing this, as well as causing undesired behavior.
fwiw, i was never able to recreate these problems, and automated testing hasn't revealed them, so i suspect that there's some errors in people's logic wrt calling on/off multiple times...