Technical support and scripting issues
Moderators: JRL, Dorian (MJT support)
-
Grovkillen
- Automation Wizard
- Posts: 1132
- Joined: Fri Aug 10, 2012 2:38 pm
- Location: Bräcke, Sweden
-
Contact:
Post
by Grovkillen » Mon Jul 29, 2024 7:36 am
I recompiled a script that now get this error. I have no way of debugging where this happens since the error isn't caught by the ON_ERROR sub routine.
According to Google it's happening because the program is trying to read memory which is out if its scoop.
Extra information: the error only happens when I run the EXE as a sub process of the main EXE. I do this to run python code which else will be eating up memory.
-
Dorian (MJT support)
- Automation Wizard
- Posts: 1414
- Joined: Sun Nov 03, 2002 3:19 am
Post
by Dorian (MJT support) » Mon Jul 29, 2024 9:56 am
This was a bit beyond me so I asked Marcus.
This is what he had to say :
If it's compiled, enable logging, run it and when the error occurs don't close error but grab log file, see where it got to
.
-
Grovkillen
- Automation Wizard
- Posts: 1132
- Joined: Fri Aug 10, 2012 2:38 pm
- Location: Bräcke, Sweden
-
Contact:
Post
by Grovkillen » Mon Jul 29, 2024 10:35 am
Ah, yes I will test that. A bit of a hassle but I manage
