Toot

Written by requiem 🏴 on 2025-01-31 at 02:46

@amd we do a lot of that 😁

I actually think it’s a fixable thing. Based on what I’m seeing, I think it’s buffering all the gcode to ram (and possibly creating multiple allocations, I don’t think there’s 10GB of gcode being produced). If instead that buffer were spooled to disk when it starts getting big I think the oom could be avoided.

That said I haven’t had a chance to look at the code yet so I could be wrong.

@djsundog

=> More informations about this toot | View the thread | More toots from requiem@hackers.town

Mentions

=> View amd@gts.amd.im profile | View djsundog@fedi.reclaim.technology profile

Tags