Open Griffork opened 3 years ago
I turned the extension back on and noticed that the problem wasn't present. I didn't enable tracing, so maybe there's a delayed infinite loop in the tracing code somewhere?
Anyway this works enough for me to use for now! Thanks!
First off I'd like to say that I LOVE this extension, to the point that I couldn't imagine developing knockout code without it.
Using the knockoutjs context debugger I'm running into a problem where the knockout extension is slowing the page down drastically, until the tab shows as using 99% CPU in chrome's Tab Task Manager.
Unfortunately I don't have a great amount of information, but due to JQuery popping up on my performance profile with a ton of knockout functions I think that the problem is a fight between JQuery and knockout (causing something like an infinite loop). For reference my site doesn't use jquery.
I've tried disabling serialisation, and it did not affect the issue. Everything runs smoothly when I disable the extension.