Lightburn crashes with this file

[LesB (Les Brown)]

Always happens when you’re in a hurry doesn’t it. I used a file a couple of days ago and needed to run it again today. But every time I try to open the file Lightburn immediatey crashes. I can open other files ok. I have tried opening the same file on another PC and same happens. So it clearly doesn’t like the file. It’s not a desperately complex file so I can recreate it but it’s a concern in case it happens with something more complex. I’m running the latest version of Lightburn (09.09). It’s on a Windows PC running Win 7pro. Info attached if it helps. Medal insert 2018 TB.lbrn (75.8 KB)

[Skerved (Vincent Skerved)]

It crashes for me too on Windows 10. Just as a reference.

[LesB (Les Brown)]

Thanks. It worked perfectly well the other day and now crashes on both my Win 7 PC and Win 10 laptop. I can’t see why that file should have been corrupted. Every thing else I have is still ok.

[Skerved (Vincent Skerved)]

I narrowed it down to line 155-157 in the file. If I remove these lines it does not crash:

<Shape Type="Text" CutIndex="2" UsesShape="2" Font="Arial,-1,100,5,75,0,0,0,0,0" Str="Couch to 5k Finisher" H="5" LS="0" LnS="0" Ah="1" Av="2" Bold="1" Weld="1">
    <XForm>1 0 0 1 320.784 215.59</XForm>
</Shape>

[LesB (Les Brown)]

Interesting. No idea how you worked that out though! Lol. Meanwhile, I have recovered the job by importing rather than opening it. When imported, the text no longer followed the paths but I just reattached the text to the paths and good to go. After I changed the date that is, which was the whole point of re-running the job in the first place!

Having said that though, finding out why there was an issue is still of interest. Next time may not be so simple.

[Skerved (Vincent Skerved)]

If I remove

UsesShape=“2”

from the Shape-thingy it also does not crash, but the text is no longer curved:

I guess the error is there somewhere, but I don’t understand the shape numbering… I guess @LightBurn do.

[LightBurn (Oz)]

This is already fixed for the next release - it has to do with the text on a path associations being saved in a funny order. I’m able to read your file without issues.

[LesB (Les Brown)]

Thanks for the explanation Oz. Looking forward to the next release. I’m sure there will be other nice things to come too.