genoverse leaves some dangling deferreds after browser.destroy() about genoverse

[simonbrent]

It's basically impossible to debug by just looking at your minified javascript, but given that call stack I would suggest adding the following:

• In Genoverse.constructor, add this.deferreds = [] below the declaration of this.events
• In Genoverse.loadGenomes and Genoverse.loadPlugins, push the returned values to this.deferreds before returning.
• In Genoverse.destroy, abort the contents of this.deferreds before doing anything else.

I haven't tested this at all, so let me know if it works!

[BurkovBA]

@simonbrent Hi, Simon.

I did as you said, but as expected, this didsn't work. By the time I destroy the browser, Genoverse.loadGenomes() and Genoverse.loadPlugins() have already fired and triggered init() and setRange(), which created deferreds on tracks, and those deferreds fire later and are not cancelled.

I'm trying to create a minimal isolated test example for you on a separate OpenStack machine. If I have time to do this, I'll contact you later on and provide a link to it, so that you don't have to setup anything. But it's also likely that I won't be able to do this as I'll be away in a few days.