Crash when deleting all objects

[MartinMue]

Version

Version of Slic3r used goes here
1.33.8
Use About->About Slic3r for release versions

For -dev versions, use git describe --tag or get the hash value for the version you downloaded or git rev-parse HEAD

Operating system type + version

What OS are you using, and state any version #s
Windows 10 64 bit Home

Behavior

Slicer crashes when deleting all objects from platter.

1. add object with the add button
2. add the same object with add button
3. change layer hight via layer editing
4. slice
5. delete all object via button Delete All

Is this a new feature request?
NO

STL/Config (.ZIP) where problem occurs

Upload a zipped copy of an STL and your config (File -> Export Config)
standard config files of this version

[bubnikv]

I cannot reproduce the issue.

Could you reproduce it every time? Is it specific to the STL shown on the screenshot?

[MartinMue]

It was reproduceable every time the other day, but i did not restart my PC during the testing.

Now i was only able to get it two times out of around 30. Does not matter which STL file.
I'l keep trying.

I'm not sure if this helps, this is how it looks like:

[bubnikv]

Thanks, it helps. I can try to iterate it multiple times. Danke.

…

On Thu, Mar 23, 2017 at 9:15 PM, MartinMue ***@***.***> wrote: It was reproduceable every time the other day, but i did not restart my PC during the testing. Now i was only able to get it two times out of around 30. Does not matter which STL file. I'l keep trying. I'm not sure if this helps, this is how it looks like: [image: today - kopie] <https://cloud.githubusercontent.com/assets/26501820/24267425/8a9e76ee-100a-11e7-9cb9-59666c42bd47.JPG> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#193 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5I8pV7QaFqd3BwnPeeRzVgDfvpda0ks5rotLHgaJpZM4MhXvg> .

[bubnikv]

I think I have found the culprit. Thanks for the report.

[bubnikv]

I have added some checks, which should avoid the crash you reported.
fdb5ed1

[bubnikv]

Please retest with the upcoming 1.35.3. If the issue is still there, please reopen this issue. Thank you.