Access violation

[jameskriebel]

Description of the bug

While slicing a new object I received a "Access violation" for the first time.

Project file & How to reproduce

This is a multicolor project, when slicing the error is produced at 90% sliced.
D4-error.zip

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

2.5.1+win64

Operating system

Windows 11

Printer model

Ender 3 Pro with a 3D Chameleon

[jameskriebel]

Possibly related to issue #10185, where I went back and re-sliced a previously successful project using the same config settings but the updated software version. That too failed but with a different error.

[kubispe1]

Hi, it is not only 2.5.1. There is an issue also in 2.6.0-alpha5+266. On my Win 10, I have the same Access violation. We will check it. Thanks

[lukasmatena]

@jameskriebel Thanks. The problem is caused by a mistake in your custom gcode:

M109 R[ttemperature[next_extruder]} ; wait until temp is reached before resuming
The combination of a legacy syntax using the square brackets, indexing something that is not a vector and the typo in the argument is too much for the placeholder parser to handle. The error check is missing in this case.

I just tried the same line in PrusaSlicer 2.2.0 and it crashes too. The bug must be there some many years.

I'm enclosing a simplified 3MF to make debugging easier: gh10183.zip

SPE-1630

[jameskriebel]

Ok, can't expect your program to overcome my bad typing. Found and fixed the typo, now sliced just fine! Thanks for the help, and love the new error in 2.5.2 which told me about my syntax error and where to find it. Thanks!

…

On Mon, Apr 3, 2023 at 5:05 AM Lukáš Matěna ***@***.***> wrote: @jameskriebel <https://github.com/jameskriebel> Thanks. The problem is caused by a mistake in your custom gcode: M109 R[ttemperature[next_extruder]} ; wait until temp is reached before resuming The combination of a legacy syntax using the square brackets, indexing something that is not a vector and the typo in the argument is too much for the placeholder parser to handle. The error check is missing in this case. I just tried the same line in PrusaSlicer 2.2.0 and it crashes too. The bug must be there some many years. We will fix it. — Reply to this email directly, view it on GitHub <#10183 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD63AIOC7RVJ5YOL32GJHULW7KHFLANCNFSM6AAAAAAWMARHXU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[FidelCapo]

This issue should be fixed and fix will be part of next release.
Closing.