I built a worker to do something that takes a long time to run.
I uses a 3rd party dylib.
When I call start it blocks the UI until it’s done.
How is this possible?
In the IDE or compiled?
Are you disabling background tasks?
No.
What about my first question?
Sorry, in the IDE.
Have you tried compiled?
No I hadn’t considered that it may behave differently.
However I think there is something else going on. I believe the dylib has some bugs and I’ve contacted the vendor. It’s causing my machine to churn so hard it gets physically hot. I know what it is doing and there is no reason it should be this intensive.
That sounds reasonable.
In the IDE, the workers run as threads, so the behavior is different.
Oh, I didn’t realize that. Hmmm. that explains an awful lot.