Slic3r goes not responding over and over Windows 10 Pro

[brotherchris]

Version

Version of Slic3r used goes here
1.33.8

Use About->About Slic3r for release versions
1.338.-prusa3d-win64

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 Pro 64bit

Behavior

• Describe the problem

Slic3r goes not responding constantly. Every other click

• Steps needed to reproduce the problem

Happens every time I use it.

• If this is a command-line slicing issue, include the options used
• Expected Results
• Actual Results
  • Screenshots from Slic3r preview are preferred

Is this a new feature request?

STL/Config (.ZIP) where problem occurs

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

3DBenchy.zip

config.zip

[brotherchris]

It appears to be the plater tab that causes the not responding. I did upgrade my intel graphics driver, but no change.

[bubnikv]

Isn't it the same issue as #233 ?
Did you update the INF files before updating the Intel HD Graphics driver?
Is the problem specific to the 1.34.1 Slic3r build, or do you have the same issue with Slic3r Prusa Edition 1.33.8?

[brotherchris]

I reinstalled the intel drivers and it seems to be working now. It happens in 1.33.8 and 1.34.1. Closing bug.

[bubnikv]

Thanks for heads up. Please note that you will likely need to update the Intel Graphics driver after each major Windows 10 update.

…

On Mon, Apr 24, 2017 at 2:27 PM, Chris ***@***.***> wrote: Closed #268 <#268>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5I1u-9KilNs6rOy76zJa-XzzUhTAKks5rzJUZgaJpZM4NFNb2> .

[bubnikv]

If you have this issue, would you please re-test with the latest beta build and report the results? Thank you.

https://github.com/prusa3d/Slic3r/releases/tag/version_1.39.1-beta1

The fix consists of removing the OpenGL glFlush() calls. The glFlush() call was superfluous, but it certainly should not lead to such adverse effects. Removal of glFlush() calls certainly solved the issue on one laptop, so let's hope it will fix all the other issues or at least most of them.

Thanks @roesel for providing a laptop for testing, it was a blessing to us.

[brotherchris]

Put the fix on, so far so good. It looks like this fixed it. Very much appreciated. I will report back if I see anymore issues.