Page MenuHome

Access Violation Exception upon import the geometry via python
Closed, ResolvedPublic


System Information
Operating system: Windows 10 Home v1803 Build 17134.706
Graphics card: NVIDIA GeForce GTX 1050 Ti

Blender Version
Broken: 2.80, e73647bf5b44, 2019-06-18
Worked: 2.80, d525c76003b3, blender 2.7 (branch), 2019-05-26

Whenever I try to import a mesh (fbx/obj) using bpy.ops.import_scene.fbx(filepath=meshPath) I get the access violation exception and the blender crashes afterward.

It is happening with an add-on that is communicating with one of our apps.



Event Timeline

Brecht Van Lommel (brecht) triaged this task as Needs Information from User priority.

I can't reproduce this.

Please attach an example .fbx file that causes the crash. And make sure the bug can be reproduced by running bpy.ops.import_scene.fbx() in the console in Blender, outside the add-on.

Running the command from the console in Blender successfully imports the file.
And if I comment out the line of code in my add-on then the blender doesn't crash. Am I missing something here? Were there any changes made to the Addons API?

There were many bugfixes, those might have caused a problem here but it's hard to say which one.

Regardless, we need a way to reproduce this on our side to be able to investigate bug reports.

Reproducing the problem would require you to sign up for a Quixel trial account here:
then download the Quixel Bridge from:
then down any free 3d asset in Bridge
and lastly export it to blender by following this tutorial:

It is a bit tedious process but I would really appreciate it if you go through with it! :)

We will not sign up for an account like that, you can try to extract a test case from your add-on code. We don't time have the time to debug full add-ons to figure out if it's an issue on our side or in the add-on.

Can I share the entire log after running the addon operation.
(I have to use blender.exe -debug-all to print out all the log information right?)

You can share the log, but it's not really what we need to investigate this bug. We need exact steps to redo the problem.

Steps are there and those are the way to reproduce the error. What else can we do or give you that may help?

Brecht Van Lommel (brecht) claimed this task.

Normally we require a .blend file and Python script that we can just run to reproduce the issue, rather than debugging an add-on to figure out if it's a bug in Blender or the add-on.

Anyway, it appears this was fixed by: rBa4c907af7760a980c09e46feed92bd93a0906ba9.

I can reproduce the crash before that, but not anymore after.

Yes, It has been fixed by the recent update. Thanks for all the help and your time! :)