@clarabellerising Already took these actions but didn't help. I've ended up reinstalling Windows. Now everything works. Hopefully won't have this problem again
BAS crashing because of Qt Error
-
@vichma said in BAS crashing because of Qt Error:
tool does not count streams
I don't quite understand what you're talking about, could you give a little more detail?
-
-
@m4zuper Should it be enough to re-install the latest version 28.7.2 or all versions, as I have multiple versions installed in parallel (sometimes the same version 2 times to open a project multiple times without conflicts). Thanks
-
@morpheus93
Sorry for the long reply.
At the very least, try installing 28.7.2 separately from the others, in a separate folder on your PC. If everything is fine, then you will have to reinstall all the others. -
@m4zuper Unfortunately installing BAS 28.7.2 on another partition does not solve the crashing issue. Also it seems that the BrowserAutomationStudio.exe process is hanging somewhere after the crash. It's not visible in the Taskmanager but blocks files and can be found and killed by a detailed process search.
-
@morpheus93 said in BAS crashing because of Qt Error:
@m4zuper Unfortunately installing BAS 28.7.2 on another partition does not solve the crashing issue. Also it seems that the BrowserAutomationStudio.exe process is hanging somewhere after the crash. It's not visible in the Taskmanager but blocks files and can be found and killed by a detailed process search.
Take a look at the BAS script logs. It looks like your app writes them very fast at startup – for example, because of some errors – and Windows kills the process.
-
@morpheus93
Can you remember what changes were made before the problems started?
Are you running the project from the BAS shell or using a compiled project?
If you are using a compiled project, try changing the compilation settings. -
@m4zuper It seemed the crash is triggered by a check for the nuber of items in a resource and a following "success" step if the resource is empty to achieve the "graceful" ending of the single threads of a multithreaded function call.
Unfortunately this causes some kind of "endless loop" as the very last thread triggers the "success" step again and again (and not as expected only 1 time) until the script crashes or Windows stops the thread.
-
@morpheus93 said in BAS crashing because of Qt Error:
@m4zuper It seemed the crash is triggered by a check for the nuber of items in a resource and a following "success" step if the resource is empty to achieve the "graceful" ending of the single threads of a multithreaded function call.
Unfortunately this causes some kind of "endless loop" as the very last thread triggers the "success" step again and again (and not as expected only 1 time) until the script crashes or Windows stops the thread.It might be that:
success == error, e.g., throw some exception with success state(?).
You ignore errors, so success are also ignored(?).
In any case, it's a very bad pattern to ignore errors in large code blocks.
