While debugging, Studio gets stuck at some point with this “invisible” dialog Windows, I don’t have an idea why and what does it mean, but I know I can press enter and then it show another one that looks the same, then press enter, then Studio closes and reopens itself.
I’m attaching screenshots and log files.
logs.7z (8.3 KB)
So inspecting more, what I get is an “Out of memory” exception.
And prior to the adding of the assignment to tio_passaAlSeguentElement variable this didn’t ever happen:
The aim of that i/o boolean variable is to be used as a trigger for the state within the circle in my “Data collection” state in the state machine project I’m working in. It’s basically “iterating” over folders, and if the directory is empty, I want it to continue to the next element. And it works. But just the 1st time or so. After that, on the next empty folder, it will stop like this.
Probably there’s some unclosed reference to something or whatever. Any hints?
This time it didn’t even stopped with the “transparent” dialog. Studio just went unresponsive; I could make this video and then stop the execution:
After stopping it, Studio is apparently usable, yet the memory consumption still is extremely high:
EDIT: Forgot to mention: extremely high… AND INCREASING. Even if my script is stopped, memory consumption keeps growing steadily.
Furthermore,
The project involves Excel activities.
When I stop debuggin, the Excel process ALWAYS stays in the background, causing further problems. Many times I have to manually end the process my self.
Is this normal behaviour? I would expect Studio to close it after I finished my debugging session…
Ah, to further make thinks funnier:
If I simply RUN the application, not debug it, I don’t get the “out of memory” error.
Nobody seems to give a damn about this issue, but I’m experiencing it every day “at nauseam”.
Whatever attempt I do to debug my app, I keep encountering these same problems like 80% times.
Excel application stays open in its own process after stopping the debugging session; I have to stop it myself.
Execution “step by step”, no matter x1 or x4 speed, stops working at a certain point.
I have to manually kill a lot of studio subprocess I don’t know why they stay there to be able to “run” something. Like the 32 bit Studio process no matter if I’m running the 64 bit version and the project is a Windows non-legacy. And several instances of the executor.
@pere if you really want to get this fixed please share a project that replicates the issue. This should also include the Excel file that is used for the data.
I don’t see any information regarding the Studio version used or the Excel file size.
Running in debugging is slower and much cpu/mem intensive since it has to read all the variables.
