4 ms·

Hey, that's not quite true. ;-) I wrote most of our javascript on firefox. My firefox has no add-ons except the Firebug. Could it be one of your extensions? H

Hey, that's not quite true. ;-) I wrote most of our javascript on firefox. My firefox has no add-ons except the Firebug. Could it be one of your extensions? Have you tried refreshing it? Which version/OS? We use howler.js to play the sounds. I have to say that I was a bit surprised to find Chrome/Safari/IE can play mp3 but Firefox plays ogg. I even had to submit a patch[1] so that howler.js can work on firefox under some weird edge cases. [1]: https://github.com/goldfire/howler.js/pull/62 https://github.com/goldfire/howler.js/pull/62

trycatch 13y ago
I tried Linux x64/FF23 and FF Nightly on a clean profile, and both leaked insane amounts of memory on this page, hundreds of KiBs per second. Interesting that according to about:memory, memory used by tab with choir.io stayed stable, but "heap-unclassified" grew uncontrollable. Bug in Firefox?
- alexdong 13y ago
  This is fascinating. Thanks for sharing. My gut feeling is that those leaks are the "socket connections" that Firefox hasn't garbage collected yet. The demo you are seeing is using long poll so there might be some good number of socket churns. FWIW, WebSocket support is high on our priority list. We just need to find the time to implement that.
CrLf 13y ago
Firefox 23.0.1 on Windows here. No extensions other than Firebug 1.12.1.
- alexdong 13y ago
  Roger.