[4.3 beta] Micro freezes

[Liger0]

Application version
4.3 beta

Platform
Win10 x64

Printer
Cr10S

Reproduction steps
Randomly, not always but pretty frequently. It happens when saving a file, opening machines, saving values, etc

Actual results
The software freezes (typical semi-blank screen) for some seconds to a minute and then continues to work normally until it re-happens

Expected results
No blockage

Additional information
It never happened on any earlier versions, 4.2.1 included.
I did a clean install of 4.3 beta.

[rburema]

I can't reproduce it here (but then again, IT just gave me a quick new laptop two weeks ago), I'll ask around if any of our other windows users have noticed this.

[Ghostkeeper]

I wouldn't call "up to a minute" micro! We would definitely have noticed this if it occurs for us. What plug-ins have you installed?

[Liger0]

Auto orientation, Barbarian units, Custom setting visibility, custom supports, mesh tool, printer settings, z offset. trimesh reader is also installed by default.

[fieldOfView]

I'm guessing you have a lot - if not all - settings visible? Could you check if the same pauses happen with just the "Basic" set visible?

[Liger0]

I have my own settings visibility with the settings I use which is the same as older Curas, also my hardware is up to the task (16gb of ram, ryzen 5 1600, vega 56), with an idle system.
I will give it a try in the spare time.

[Ghostkeeper]

We haven't been able to reproduce this yet on any of our Windows or Linux computers. Our only known freezes (afaik) are:

• When adding a printer. It needs to lazy-load a whole lot of profiles then.
• When compressing g-code for sending via wifi or UFP. Just a lot of data to compress.
• When changing the number of extruders of a printer. A lot of profile lists need to get updated then.

To fix this, we're going to need to find some patterns in different users that have this problem.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.