I too was having issues with weird stalling on rapids in Gcode. Worked great with jogs.
A few months back i started seeing the issue, after I upgraded past 2.48 to 3.043.022
Well, it came back today on a critical "one shot one kill MIL job I have to get out tonight. Thank god I did a dry run with a laser edge finder (the job is a bear - trying to line up stuff on an already machined box)
I heard it stall on a diagonal. Always the same line. Rest of the code ran great.
After putzing around with this and that in 3.043.066 today (saw it back months ago thought .066 fixed it - wrong it turns out)
Went back to 2.48; did a full uninstall - reinstall, (restored my back ups of the macros sub dir and my xml from that version - thank god I'm anal about backing up stuff and keeping old cfg's)
No issue.
It's only on code rapids, where the x and y are at different speeds. Only happens with certain rapids; when it does it's fairly consistent - it always stalls at the same place, same ammount - the stall leaves the axis at the same wrong machine coord. In this case it was 220mil off. Every time.
If it were some marginal thing with hardware, pulsing, etc... it'd be more random. Nope. If you changed a pulse rate, pulse width, etc... it'd change but repeated runs would then lose the same distance.
Something went amiss in the version 3 build. It could be PC/OS environ specific. Maybe there was something in Arts original code that was a bit fragile, dependent on some compiler, machine config, chipset, etc... dunno.
But I'm sticking with 2.48. It works. I ran 2.48 for quite a few years, hundreds of jobs with it never had an issue.