Gettextinit freezes debugger

[cvlr]

GetTextInit
ArrayDim>Trailers,1
If you start with F8 at the top it will pause at GetTextInit and go no further. If you Run the program and there is an ArrayDim command anywhere before or after GetTextInit it will run but then MS becomes unstable and starts to have repaint issues on the screen and eventually will give an out of memory or out of system resources messages. It also does other things like variables stop incrementing. For instance Let>i=1
then Let>i=i+1 will not increment. It stays 1. Sometimes you will get a -1 but I haven't figured out a commonality to that yet.

I am not out of system resources....

Basically anytime you have ArrayDim in the same script running with GetTextInit it will cause MS to behave erratically and eventually lock up.

[Dorian (MJT support)]

I just replicated some anomalies with this too. Oddly, not on the first runthrough. It took a few times. I will mention this to Marcus.

[Marcus Tettmar]

I cannot replicate. Would kind of help to know which Macro Scheduler version and which version and bitness of Windows.

[bnc1]

I have a similar problem with Gettextinit and WaitKeyDown. Macro Scheduler becomes unstable with false low on memory errors. I am running MS 14.5.5 and Windows 10 ver 1909.

[Dorian (MJT support)]

I have a similar problem with Gettextinit and WaitKeyDown. Macro Scheduler becomes unstable with false low on memory errors. I am running MS 14.5.5 and Windows 10 ver 1909.

Is that 64 bit Win 10?

To check whether you’re using a 32-bit or 64-bit version of Windows 10, open the Settings app by pressing Windows+I, and then head to System > About. On the right side, look for the “System type” entry.

[bnc1]

I am running Windows 10 v1909 64 bit.

This problem may be related to changes to Macro Scheduler GetWord text dlls in v14.5.5 of Macro Scheduler. I can not replicate the issue in v14.5.4. The GetWord text dlls were upgraded from 4.1.2.192 to 5.1.1.251 .

The exact MS error messages are "Out of System Resources" or "Not enough memory resources are available to process this command". My scripts seem to execute but eventually MS becomes unstable. This is similar to what the original poster had observed.

[omlavi]

I have a similar problem with Gettextinit and WaitKeyDown. Macro Scheduler becomes unstable with false low on memory errors. I am running MS 14.5.5 and Windows 10 ver 1909.

Hi, I seem to be having the same problem with Gettextinit. I'm running 64bit Win10 pro.

Thanks!

[bnc1]

I continue to have this same problem with Macro Scheduler v15.0.09. Scripts with GetTextInit will eventually cause my MS session to become unstable with error messages "Out of System Resources" or "Not enough memory resources are available to process this command".

On my systems this issue started with v14.5.5 of Macro Scheduler, when the GetWord text dlls were changed. I can not replicate the issue in v14.5.4.

[Marcus Tettmar]

I have reached out to the developers of the text capture library to see if this is a known issue or if there is an update available.

[omlavi]

I have reached out to the developers of the text capture library to see if this is a known issue or if there is an update available.

Thanks a lot! It will allow me to switch from image recognition to using gettextatpoint and will help me very much.

[Marcus Tettmar]

Hi,

Please could you try this version of the text capture distributables:
https://www.dropbox.com/s/hr5xet6kxftgy ... 1.zip?dl=0

Please fully exit Macro Scheduler (file/exit or exit from system tray). Then extract the files in the zip file above to your Macro Scheduler 15 program folder (overwriting existing copies - backup first if you wish - or we can always reinstate with a reinstall). Then restart and see if the problem persists.

[bnc1]

My test with Gettextinit and the new text libraries failed with the same problem previously posted

[Marcus Tettmar]

Ok thanks for that. I'm sorry to hear this. I was assured an issue with a handle leak was fixed. But perhaps that isn't your issue. I will feed back again and we will do more tests here.

[Enricoys]

What is the status of this issue? I observe exactly the same using this code: repaint issues and out of resources. Only solution is to kill MSched using the Task Manager. I use Windows 10 pro (10.0.18363) x64 and Macro Scheduler 15.0.13.
Actually, I started to observe those issues in my scripts since I start using version 15. My standard way of debugging is that I always kill MSched by using the Task Manager after each debug session. Otherwise the system becomes very unreliable (even lost twice my complete Macro Scheduler map ). I was never able to find the reason for such behaviour, but now it is clear to me that this is the same issue as mentioned here. After having used more than 100 times the Task Manager to kill MSched I am really looking forward for a final solution.

[Marcus Tettmar]

I'm afraid there still seems to be a memory leak affecting some people in the text capture libraries. These are provided by a third party and we have reported back to them. They claimed to have fixed it but the problem persists. I will continue to nag them. I'm afraid they are not very responsive.