I played a bit with it, and I still get corrupted meshes. This bug typically happens with large files, but unfortunately I can't reproduce it reliable. Sometimes it works, sometimes it doesn't. Here is a 150M STL file that triggers it almost every time: https://1drv.ms/u/s!Au1u53SHpLowjGhzY5Npp1DNAW6k?e=LYbvEk

Sometimes it works, sometimes it doesn't.

@gebner

1. Statistically how many times do you have to try to get corruption? Just so I know how much time to spend to repro it.
2. Do you need to quit Cura in between?
3. Is there an upstream bug report?

Hello, I'm a bot and I thank you in the name of the community for your contributions.

Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:

If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list.

If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past.

If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments.

Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel.

Still important, but knowing whether there's an associated upstream bug report would be very useful.

Still important, but knowing whether there's an associated upstream bug report would be very useful.

I'm not aware of any upstream bug about this issue, or even what upstream is in this case:

• Cura only accepts bugs that are reproducible with their appimage. And they build openblas without openmp, thereby avoiding this bug.
• It's possible that the bug is due to how PyQt sets up threads, who knows?
• The other options are scipy or openblas. However they likely want a small testcase triggering the bug (i.e. not involving cura). I simply don't have the time to minimize this in the foreseeable future.

Statistically how many times do you have to try to get corruption? Just so I know how much time to spend to repro it.

It happens more than 50% of the time, larger meshes are more likely to be corrupted.

Do you need to quit Cura in between?

No.

I marked this as stale due to inactivity. → More info