I would politely suggest stopping messing with the Slicers, unless you really found this interesting.
If you read the stack trace in any log file, you would realize it is crashing inside the BED_MESH call.
Which is called inside the PRINT_START macros.
So, as long as PRINT_START is called and the BED_MESH_CALIBRATE is called, it would crash.
So, as long as ANY slicer calls PRINT_START, it would crash.
Hope that helps a little.
About the issue itself. Well: The "dirty" Flag and the Team's Position
There should be a goodwill to read the scanner.py code and sometimes guess what is wrong.
Which is complicated if you do not have one. I can’t find anything suspicious from a brief look.
I may only suggest changing the bed_mesh speed 500 -> 100.
But I honestly have no idea how or why it is triggered here.
Maybe speed reduction would help, idk.
I’m using a simple analog inductive probe and also using the high movement speed (400mm/s).
So, the mainline code should work here.
From my small calculations, I do think, that OID=8 it is one of the XY motors.
# queue_step oid=8 interval=1594 count=986 add=0
>>> 1594 / 180000000
8.855555555555555e-06
>>> print("%.9f s" % (1594 / 180000000))
0.000008856 s
>>> 40 / 200 / 32
0.00625 # mm per step
>>> 1 / 0.000008856
112917.79584462511 # Steps per second
>>> 1 / 0.000008856 * 0.00625
705.736224028907 # 705 mm/s - diagonal XY movement. 500 * 1.44 = 720.0