1
Debugger mass printing errors for empty variables
complete
Greg Florkow
Debugger console started producing warnings for empty local variables "node value output already exists".
Start a vanilla new app, create a local client storage database and add it to any page.
Once you start the debugger the console will printing "node value output already exists" every 5 sec as per default on data flow. I had 2-3 databases on one of the page with 2 sec delay, so you get a constant stream of data - which at some stage crashes the debugger.
This must be from a new update as I have not seen it before.
Log In
Activity
Newest
Oldest
H
Harri Sarsa
complete
This should now be fixed, sorry for taking a while!
A
Anthony Williamson
Spent the last hour or so combing through the app. I thought it was something I did, or didn't do... lol
H
Harri Sarsa
We'll work to get to this ASAP, sorry for the delays!
Greg Florkow
@Harri Sarsa is it possible to do something about this warning? it keeps producing rows of data which drastically slows down the debugger, eventually crashes the browser windows with appgyver.
Greg Florkow
@Harri Sarsa This warning after repeated polling of local variables - does make the debugger crash. It gets in a way of debugging.
H
Harri Sarsa
planned
H
Harri Sarsa
I think this is a side effect of us updating the internal functionalities of many of the flow functions, we'll investigate!