Page MenuHome

Vertex crease dropdown option issue blender 3.1 / 3.2 macOS
Closed, ArchivedPublic

Description

System Information
Operating system: macOS-12.2-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.103

Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-02-04 00:27, hash: rB28656293c624

Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-02 15:25, hash: rB43b0ff3054ba

Short description of error
blender crashing when using vertex crease option from the edit mode dropdown menu (NOT the N-Panel)

Exact steps for others to reproduce the error
Take a cube, subdevide it with a modifier, go to edit mode and select a vertex.
USE the 'Vertex Crease' option from the Vertex dropdown menu in edit mode (not the n-panle) and drag your mouse back and forth.
Crease level will be only updated in the info section top left from viewport, BUT not on the mesh PLUS after a few secons dragging the mouse, blender will crash.

Event Timeline

Omar Emara (OmarSquircleArt) changed the task status from Needs Triage to Needs Information from User.Feb 7 2022, 2:07 PM

I cannot reproduce this with either the latest stable or current development versions of Blender:

Please try the latest daily build: https://builder.blender.org/download/

Go to File โ†’ Defaults โ†’ Load Factory Settings and then load your file to see if you still can reproduce this issue.

If the problem persists, please give us more clear instructions on how to reproduce it from scratch.

Guido (Nurb2Kea) added a comment.EditedFeb 7 2022, 2:43 PM

Did this already before sending the bugreport :-)
It happens with factory & personal settings with blender 3.1 / 3.2

Plus with the latest blender just compiled. --- MACOS 12.2 --- INTEL ---

blender the ay before build --- MACOS 12.2 --- INTEL ---

Omar Emara (OmarSquircleArt) changed the task status from Needs Information from User to Needs Triage.Feb 7 2022, 3:16 PM

I still can't reproduce unfortunately.

I still can't reproduce unfortunately.

If I may ask: What Operating Systemm you use to check this issue?
I'm using macOS as stated.

I tested on Linux. But the issues seems to be OS agnostic.

I tested on Linux. But the issues seems to be OS agnostic.

Nope, I don't think so.
Just last week they published for macos without testing it. (Because not every dev. has a mac to check)

So please just leave it to someone who can test it on MACOS.
Otherwise you change the status of this bugreport without the ability to test it under the conditions stated in the bugreport.

Thanks

That's fine. I just changed it to Need Triage so someone else can pick it up.

@Ankit Meel (ankitm) can you check?

No issues on windows too.

mesh shows updates, no crash . macOS 12.2 blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg
lite + asan + opensubdiv is also fine c146d75808f84fddeffb0059b31e572845a3bc49

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Feb 16 2022, 11:42 AM

Since we are not able to reproduce yet, have to ask again: Is this still happening in a fresh build from https://builder.blender.org/download/daily/?
Can we see this in action with Factory Defaults?

Did this already before sending the bugreport :-)

The crash text is also provided by me ! (See first post)

Anyways, this tests to set everything back cost me every time 1-2 hours. per blender version.
I'm not a huge addon fan, but all the personal settings are all the same. since blender 2.93 versions
The bugs arrise with new alpha/beta releases.
So I test both, what I did. And if there is something changing I report it.

IF WE COULD SEE What changes made with each release on what OS, we could pinpoint the bugs/bugreports way better.

As far as the mac support goes here, I've decided to wait until...I find a reliable mac dev.
Because we will definitely have lotz more apple mac users in the future as we know and mac needs the same affection as windows.

Thanks for the help so far.

Anyways, this tests to set everything back cost me every time 1-2 hours. per blender version.
I'm not a huge addon fan, but all the personal settings are all the same. since blender 2.93 versions

You shouldnt have to do this, just use File > Defaults > Load Factory Settings, check the issue/bug, close blender. If you then start blender again, your previous preferences should still be there (is this not the case?).
To be extra safe, you could make sure that Auto Safe Preferences is OFF -- but again: this shouldnt be neccessary

So I would still think it would be good to test this in fresh builds with Factory Defaults (because the last weeks commits in this area might actually make a difference here).

Thanks for the info..not the first time on blender.
If you can't reproduce it AND say: (because the last weeks commits in this area might actually make a difference here) , makes no sense but me wonderering!

Thank you. I can still adjust it in the N-Panel.

Someone can close the bugreport or delete it if you decide so. Reason: see above post.

Thanks for the info..not the first time on blender.
If you can't reproduce it AND say: (because the last weeks commits in this area might actually make a difference here) , makes no sense but me wonderering!

Thank you. I can still adjust it in the N-Panel.

Someone can close the bugreport or delete it if you decide so. Reason: see above post.

?

To get this straight: there is probably an issue (nobody doubts this), and we are trying to get to it by asking you to check something.
I cannot reproduce it, yes (I'm on linux). Could the commits from last week make a difference for macOS: possible
Could Addons (or certain preferences) still have an influence here: possible
So we still have not tested in a fresh build with Factory Defaults, will wait until this is done, thx in advance

Ok, understood!

One question to understand better:

If there are changes in the code that could affect macos ((made on a different OS)), why aren't these chages get tested on macos before release on the website or for compiling.
Isn't there a macos machine available for blender dev's via remote or virtual machines to test those changes quick before release. That would be a matter of 5-10 min. i guess!
Would make sense, to save a huge ammount of time and brain cells, if not.
I had this now the third time that devs. told me they have no access to macos.

There are automated unit tests (run on buildbots on all OSes), but these dont catch every possible error

IF WE COULD SEE What changes made with each release on what OS, we could pinpoint the bugs/bugreports way better.

That is easy, just take a look here: https://developer.blender.org/diffusion/B/history/master/
There are ALL the changes.
Blender is very transparent, you can take a look in almost every corner of the development.

IF WE COULD SEE What changes made with each release on what OS, we could pinpoint the bugs/bugreports way better.

That is easy, just take a look here: https://developer.blender.org/diffusion/B/history/master/
There are ALL the changes.
Blender is very transparent, you can take a look in almost every corner of the development.

Thank you, that makes it a lot easier. :-)

Philipp Oeser (lichtwerk) closed this task as Archived.Mar 24 2022, 2:51 PM

So we still have not tested in a fresh build with Factory Defaults, will wait until this is done, thx in advance

Sorry, but since this was still not done, afraid we have to close.
Feel free to comment again if this was checked, we could always reopen in such case.