Gettextinit freezes debugger

[Enricoys]

Hi Marcus, can you tell when more improvement can be expected on this subject. I use 15.0.16 (on Win10 64 bit) and still remain to have the same issues. Clearly related to Gettextinit. As long as I run the script without calling Gettextinit I can continue debugging as normal. As soon Gettextinit is called the MS software gets very unstable during debugging (out of resources, repainting issues). Most often I need to kill the MS process after a few debug sessions to prevent even more serious issues.
Nevertheless I still very much enjoy this software. Great job!

[Dorian (MJT support)]

The situation is still the same. I had a report of it this morning. The usual workaround is the newer OCR functions.

[fightcancer]

So glad to find this thread as MS v. 15.0.18 crashes constantly (and only) when I use GetTextInit and GetTextInRect!

[Djek]

Just to let you know; I also experience this problem.

The use of “GetTextinit” makes Macroscheduler unstable, and looks randomly but fast to result into the “out of System Resources” and “Not enough memory…” errors popping up. Nothing left to what you can do is to kill the process MSched.exe in the systray taskmanager.

I am running Windows 7 64 bit
MS pro version 15.0.18 – April 2021

Kind regards,
Djek

[Maluel1]

Thanks to everyone on this post. I at least know to avoid using gettextinit. I was using it for reading a text file to retrieve a large sql statement. Out of system resources and all the other errors mentioned have been seen on my computer. I'm noticing it causes my WaitScreenImage say..invalid parameters after successfully running for many hours.

[Marcus Tettmar]

To read a text file just use ReadFile ...