likely

but even commenting out the two things that are nulled it continues... hmm 🤔

it could be a thread issue, although, apart from this the threading in core/http has been fine?

yeah everything has been fine

ok, so maybe its not that then, as if it was, i would have expected you to have bizarre issues in other places when updating the UI

it seems like it is an issue with setting main_timer to null

which is odd

so yeah, my guess is that once the http call finishes something is off

cause i don't reference main_timer in any http request

what does main_timer do?

could be a race condition

```hx public function run(url:String) { main_timer = new Timer(200, () -> { if (!active) { if (!preloaded) { active = true; this.loadSearchStats(url); } if (!this.requested_all_search_pages && preloaded) { for (url in preload_search_pages) { this.getProductLinks(url); } trace('got all pages'); this.requested_all_search_pages = true; } if (!requested_all_products && product_links[product_pos] != null && requested_all_search_pages && preloaded) { active = true; this.getProductPage(product_links[product_pos]); } if (product_pos == this.product_links.length && this.product_links.length > 0) { requested_all_products = true; } } if (requested_all_products && this.data.length >= this.product_links.length) { trace('done'); this.completed = true; main_timer.stop(); } this.update(status); }); } ```

basically an update loop

nothing in here would make me think there's an issue

at least imo

its hard for me to grep that fully, but i feels like it could intefer with threads... like what does "getProductPage" do? Is that making an http request?

yeah

so yeah, that seems like a race condition, no?

but aren't timers synchronous?

?

not at all.. they are async, other wise they would be holding up the main thread

Sys.sleep is sync

you might want to consider gracefully handling the timer shutdown... ie, flag it for "complete" and stop / null it once all threads have finished. Honestly, you shouldnt really need to, but i dont really understand the app or what its doing

yeah, it seems to work fine at first glance if i stop the timer rather than null it

i think that makes sense... maybe if you null it then it stops it and clears its callback (its an assumption)

but oddly, the async requests affect the next time I hit "start" despite using a new class 🤣

ie, it gets GC'd

so it still exists "somewhere"

yeah, i mean, i dont know fully what the app is doing, but you might want to reconsider this main timer... go for a queue or a pool or something

lets see what happens if i stop the timer then null the instance