Error: https://i.imgur.com/Qb6EVHU.png
Layout: https://i.imgur.com/MsXIz0S.png
So, I was doing a test that I was chatting with @th33xitus about over on the Klipper Discord earlier this week (having a smaller object inside of a larger object and then excluding the larger object, to see if the visual depiction was as expected or not, and if the inner object was still printed - yes to both - EO Screeny: https://i.imgur.com/T1lGald.png).
Anyways, I found that as the smaller object (shorter in Z too) was completed, with the only other item in the gcode being the excluded object, the printer kept processing gcode and making rapid continuous Z-height adjustments consistent with the layer changes on the rest of the print - just the excluded object in this case. So I am guessing that this might be an edge case, but I did see see the error as depicted herein - which caused a cessation of print commensurate with the error. I suspect that if I had other items being printed, it might not have overwhelmed the buffers/mcus with these rapid Z-axis changes due to the cancelled object gcode not being executed (except for said z-axis changes (material printing stopped at Layer 82, with ~50-ish non-printing layer changes before it borked)). Maybe having to command the 4 z-steppers concurrently and rapidly is what caused the ‘overrun’.?.
My point in posting is to inquire if this is worthy of a bug report on github, or just one of those things where the doctor will say ’ Well, if it hurts, don’t do that…’
Thoughts?