Infinite loop in watch.js:64

[TheBox193]

I appear to be running into a similar issue to #14 , however I'm unsure how I can get more info for debugging to find the cause and possible solution. It appears to be related to views where I have a collection and have a model that stores pagination information, but beyond that I'm not sure what action in my code is causing it Backbone-Debugger to enter an infinite loop in watch.js:64. It doesn't seem I can open watch.js in Chrome dev tools to dig in further. Any tips on debugging Backbone-Debugger?

Uncaught TypeError: Cannot read property 'perpage' of undefined watch.js:64

[Maluen]

@TheBox193 as first thing you may want to look at some of the latest watchjs issues, especially the Infinite loop on pushing to array #67 one that seems to be similar to what you are experiencing. Not that there are lot of info on how to fix this on that page.

As second thing, would be very useful (or even needed) if you were able to create a minimal example that reproduces the bug, like how was did on #14.

As alternative / addition, would be also quite useful if you were able to share the application url (if any) so that I can look.

The problem you are experiencing seems to be related to the backend side of the extension, specifically to the injected script, as far as I know there is no easy way to retrieve this in the sources tab of the devtools, but you can add "debugger" statements into https://github.com/Maluen/Backbone-Debugger/blob/master/js/lib/watch.js or any other specific file you want to debug and should work just fine.