Page MenuHome

Entering edit mode on a mesh after initiating shrink wrap modifier +mirror crashes program
Closed, ArchivedPublic


System Information
Operating system: Windows 10
Graphics card: GE Force GTX 1050

Blender Version
Broken: 2.80

Short description of error
Once you initiate a shrink wrap modifier +mirror on a mesh to another target *that has mirror modifier also*, if you enter edit mode on it, the program abruptly crashes

edit: additional info- Actually applying the mirror modifier to the object does *not* change this behavior. The bug gets baked into the new mesh.

Exact steps for others to reproduce the error
-Create any mesh, apply mirror modifier.
-Create another mesh and apply mirror modifier, and then select the shrink-wrap modifier targeting the former.
-Press tab to enter edit mode on the latter.
This happens consistently with target being a cube and second mesh being a plane. Haven't really tried other cases but it crashes my model so I'm assuming it doesn't work for any.



Event Timeline

William Reynish (billreynish) triaged this task as Needs Information from User priority.

Can you supply a blend file that demonstrates the issue?

If you select the plane and press tab, it should crash. At least it does for me.

Later today I can dig up the old file for the model I'm working on and show that anything that has ever had a mirror modifier at any point in time crashes the program this way. I had to remake a ton of little assets without mirror, buts that's my own fault for using beta!

On ubuntu 16.04 64 bits, NVIDIA Titan Black, with 2.80 hash 382b2a

I can't reproduce from scratch. No crash with attached .blend file.

Blender should produce a .txt file into tmp folder when crashing.
Can you attach it, too ?

I don't see a .txt file in my /tmp directory when running blender normally. Oddly enough, when I run the file in debug mode, Blender does not produce the "EXCEPTION ACCESS_VIOLATION" error and crash. I attached that report anyway.

I doubled+triple checked running the file not in debug mode and it still crashes.

If it helps, I'm working on a 13" Microsoft Surface Book 2. If this is something that another Windows computer can't reproduce, it could be possible that it's unique to this series of computers: I've had trouble running software like Mathematica with CUDA enabled because the OS gatekeeps access to the GPU and tries to force i7 use. I'll try looking into this a bit myself.

Kelly (kiwiwikikwi) added a comment.EditedApr 3 2019, 9:28 PM

Clean install of NVIDA drivers + instructing the OS to use GE Force GTX 1050 in Blender 2.8 did not rectify problem. So, the naive solution doesn't work, but it doesn't mean its not GPU related because I still can't do parallel processing in Mathematica with these settings either... (I gave up on this because it's an absolute mess to sift through with my limited experience)

I'm guessing debug mode is somehow compiled differently so that's the only hint towards what's causing the crash.

Let me know if there is anything I can provide on my end to help

Brecht Van Lommel (brecht) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Apr 9 2019, 1:37 PM

Can't reproduce this either (no obvious ASAN issues either). @LazyDodo (LazyDodo) do you have any luck?

I get crashes in 2.8 pretty frequently, especially when toggling between edit/object mode on meshes with modifiers etc. Sometimes it happens 5-10 times in a work session and I rage quit. I just assumed that this was because it's in beta, but I see you guys are in the homestretch to release...

Now I'm wondering if my crashes are all related and have to do with my hardware.. I'll have to try working on my secondary computer to see if I have the same issues.

Sebastian Parborg (zeddb) triaged this task as Needs Information from User priority.Jun 11 2019, 12:04 PM

Is this still an issue?

Demeter Dzadik (Mets) closed this task as Archived.
Demeter Dzadik (Mets) claimed this task.

Closing for now due to no response in a long time. Feel free to re-open if this is still an issue. Hopefully it was fixed somewhere along the past few months.