Maniphest T65921

Access Violation Exception upon import the geometry via python
Closed, Resolved
Actions

Assigned To
Brecht Van Lommel (brecht)
Authored By
Mian Ajwad Imran (ajwad_quixel)
Jun 19 2019, 10:47 AM
Tags
  • BF Blender
Subscribers
Brecht Van Lommel (brecht)
Jon Be (jonbra)
Mian Ajwad Imran (ajwad_quixel)

Description

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.

Related Objects

Mentioned Here
rBa4c907af7760: Fix T65806: Can't Access bpy.context inside Application Timer
rBe73647bf5b44: Move to Collection: Fix tooltip

Event Timeline

Mian Ajwad Imran (ajwad_quixel) created this task.Jun 19 2019, 10:47 AM
Brecht Van Lommel (brecht) lowered the priority of this task from 90 to 30.Jun 19 2019, 1:25 PM
Brecht Van Lommel (brecht) added a subscriber: Brecht Van Lommel (brecht).

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.

Mian Ajwad Imran (ajwad_quixel) added a comment.Jun 19 2019, 1:46 PM

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?

Brecht Van Lommel (brecht) added a comment.EditedJun 19 2019, 2:00 PM

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.

Mian Ajwad Imran (ajwad_quixel) added a comment.Jun 19 2019, 2:22 PM

Reproducing the problem would require you to sign up for a Quixel trial account here: https://quixel.com/signup
then download the Quixel Bridge from: https://quixel.com/bridge
then down any free 3d asset in Bridge
and lastly export it to blender by following this tutorial: https://www.youtube.com/watch?v=u6RqgbiZ3ts&

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

Brecht Van Lommel (brecht) added a comment.EditedJun 19 2019, 2:42 PM

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.

Mian Ajwad Imran (ajwad_quixel) added a comment.Jun 19 2019, 3:17 PM

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?)

Brecht Van Lommel (brecht) added a comment.Jun 21 2019, 11:53 AM

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.

Brecht Van Lommel (brecht) merged a task: T66098: Quixel to Blender live link making Blender Crash / or not importing anything..Jun 25 2019, 12:49 PM
Brecht Van Lommel (brecht) added a subscriber: Jon Be (jonbra).
Jon Be (jonbra) added a comment.Jun 25 2019, 5:28 PM

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) changed the task status from Unknown Status to Resolved.Jun 25 2019, 6:40 PM
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.

Mian Ajwad Imran (ajwad_quixel) added a comment.Jun 25 2019, 6:42 PM

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