Page MenuHome

Carver MT addon AV's when attempting any of its operations
Closed, ArchivedPublic

Description

System Information
Win10 (AMD Mobility Radeon HD 5000)

Blender Version
Broken: version: 2.79 (sub 1), branch: master, commit date: 2017-09-17 08:00, hash: 9134529, type: Release
Worked: N/A

Short description of error
The Carver MT addon AVs when attempting any of its operations

Exact steps for others to reproduce the error

  • Start with the default cube scene
  • Enable the "Carver MT" addon
  • Switch to an orthographic view
  • Hit CTRL+SHIFT+X to start the addon
  • Click and draw a rectangle over top the default cube
  • Crash (Error: EXCEPTION_ACCESS_VIOLATION printed on console)

Details

Type
Bug

Event Timeline

Vuk Gardašević (lijenstina) triaged this task as Needs Information from User priority.Oct 9 2017, 2:10 AM

I could not recreate it on the build 5c6e3ff from 28 September on Win 7.

Can you please try the latest appropriate build from https://builder.blender.org/download/ (the first section at the top)?

Marking as incomplete until additional information is provided.

Ok, I tried again, here's some more interesting information:

  • Broken: Experimental Build Branch by VS 2015 (Windows Vista/7/8/10) blender-2.79-83ce028-win64-vc14.zip
  • Worked: Official blender-2.79-83ce028-win64.zip

It's odd that the compiler change seems to have resulted in instability in this area -- The VS 2015 version has been working fine for me otherwise. If that build is going to become official one day it's probably worth looking into now and/or switching directly to VS 2017 (VC15) etc. to see if that's still affected.

I can't seem to repro with the exact build you mentioned. Couple of things to try

  1. start blender with the --factory-startup parameter and see if it's a local setting somewhere
  2. maybe it's a bad gpu driver, grab a software opengl implementation from here and copy it into the blender folder, then start blender and re-try. (be sure to remove the dll once you are done testing, cause things will be *VERY* slow)

Could not reproduce it either with both the default compiler and the vc14 latest builds.

In addition to the previous comment, can you also attach the system-info.txt generated from the Help> Save System Info menu by dragging and dropping the whole .txt file into the comment field ( do not paste it's contents directly in the comment field it is difficult to read and breaks up the formatting).

For some further reading about how to attach files to reports check the link here:
https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports (under the Appending files to the report section)

I'm away from my laptop, however, I can reproduce the problem on my office desktop as well -- same crash using the vc14 builds. System is Win10, nVidia Quadro 600 this time.

Attached are 2 system-info files, there's not much difference though...

  1. maybe it's a bad gpu driver, grab a software opengl implementation from here and copy it into the blender folder, then start blender and re-try. (be sure to remove the dll once you are done testing, cause things will be *VERY* slow)

Sorry for the late response, did you manage to test with the software renderer like it was suggested in the quote of one of the posts above? As that will point out to a GPU driver issue.

Yup, same crash with using the, very slow, opengl32.dll

It doesn't seem GPU related as I get crashes on both AMD (laptop) and nVidia (pc) machines.

From the given information so far the other possibility is that the userpref and startup blend files got corrupted somehow (that can happen if for instance a developer build was used and those files were saved). Try to backup the 2.79 folder in Users\SOME USER NAME\AppData\Roaming\Blender Foundation\Blender\ and move it completely from there so there is no 2.79 config. That will force Blender to start with factory settings. Try to enable the add-on then.

Sorry again for the late response. If that is not the cause, I'm not sure what the issue could be.

Bastien Montagne (mont29) claimed this task.

More than a week without answer, cannot reproduce either with current master, debug build with ASAN enabled (tried both Carve and BMesh solvers), and since two other people tried to reproduce and failed… Am sorry, but I’ll archive this, we need to be able to reproduce an issue to investigate it. Indeed, most likely explanation would be a corrupted startup cube (you can also start in factory settings from a command line with --factory-startup option, instead of nuking your 2.79 folder ;) ).