3 ms·
The demo site is also leaking (a lot of) memory. Use the "heap snapshot" in Chrome Dev tools [1] and do some heap comparisons when going from one page to anothe
by gildas 14y ago
The demo site is also leaking (a lot of) memory. Use the "heap snapshot" in Chrome Dev tools [1] and do some heap comparisons when going from one page to another one (switch between two distinct pages multiple times).
[1] https://developers.google.com/chrome-developer-tools/docs/heap-profiling#views_dom https://developers.google.com/chrome-developer-tools/docs/he...
- rolux 14y agoHey... I assume you're referring to 0xDB.org. That may be a bug in pan.do/ra (the application), rather than in OxJS itself. We fixed some memory leaks recently, but may have missed some. If you care to provide a few more details (via e-mail, or using our bug tracker), we're definitely going to look into it.
- gildas 14y agoNo I was refering to your examples. I sent you a mail to show you how to reproduce the problem.