hi! you can add a counter (an atom) which increments no a function and a throw when that counter goes over some threshold and then look at the recordings to see why it isn't stopping

I guess we should bring back the FlowStorm ability to not only stop recordings but also throw after a thread limit to break infinite loops/recursions

I tried a counter but the places I suspect didn't seem to work. I might be missing the loop.

you can always resort to a couple of console.logs to see that those parts are repeatedly being called, once you see there is repetition there you can :

(def cnt (atom 0))
(defn break-on-limit []
  (when (> cnt 1000) (throw (js/Error. "limit exceded")))
  (swap! cnt inc))

(defn one-of-your-functions []  
  (break-on-limit)
  
  ...)

Here's what I do in similar situations: 1. Keep the DevTools panel open on the Sources tab (at least, that's what it's called in Chrome) 2. Trigger the recursion 3. Press the Pause button in the Sources tab 4. Check the call stack

that normally doesn't work for me @U2FRKM4TW on busy loops since it freezes the entire devtools

In Chrome as well? Because it definitely worked for me on busy loops, multiple times. Maybe not on for (;;) {} but when calling functions - definitely.

I'll give it a try

yeah that is the thing, it depends on the kind of loops, if you do a (loop [] ... (recur)) it doesn't work for me on Chrome nor Firefox

It looks like it somewhat worked I'm investigating the call stack now 🙏

oh nice! I guess I shouldn't completely discard that technique then

couldn't find the culcript though... I somehow figured out its related to some collection I'm trying to render for each child it enters an infinite recursion but I can't findout where \ how

can you cut the process with the counter and exception technique?

I can't seem to place the counter in the right place 😕

have you tried adding a (js/console.log ...) first to make sure that the code is going multiple times over there, then you could add the counter and throw the exception. Maybe your loop is related to events handling? so some action fires an event, which when handled does something that fires more events?

If every approach that you try fails, try at least to create a minimal reproducible example - I'd be curious to check it out.

in firefox the html inspector shows you all events registered on the dom, and you can break on them. Or in ClojureScript you could add a bunch of (js-debugger) statements, which will generate a javascript debugger; statement. Then you will be breaking everywhere, maybe that helps

if that doesn't work I can push pretty quickly a FlowStorm commit that will throw (instead of stop recording) after you set a limit. So there shouldn't be escape to that since all instrumented instructions will throw after the limit is reached and you should be able to explore recordings

The problem with my code is that it has a couple of layers and the bottom layer is basically a framework for the layers above it. While it passes a lot of tests and use-cases there are still (and probably always will be) some edge cases that causes it to break. Trying to debug a function there is very similar to trying to debug get , I hit it thousands of times before I get to the problamatic pattern. I'll try to reduce the context of the test case in order to debug it

Maybe I'll move my debugging efforts to the higher layers

let me push one commit to FlowStorm master that hopefully will help with that

@U8RHR1V60 ok, on master you have this now

so, if you check the throw on limit, all instrumented instructions will throw when the limit is reached

just tried it on ClojureScript also and seems to be working fine

🙏 I'll give it a try and let you know how it goes

It worked, now I'm playing with the numbers to get enough into the loop but not enough to crash

great! happy bug hunting!