Access Violation Exception upon import the geometry via python #65921

Closed
opened 2019-06-19 10:47:12 +02:00 by Mian Ajwad Imran · 15 comments

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

Blender Version
Broken: 2.80, e73647bf5b, 2019-06-18
Worked: 2.80, d525c76003, 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.

**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.

Added subscriber: @ajwad_quixel

Added subscriber: @ajwad_quixel

#66098 was marked as duplicate of this issue

#66098 was marked as duplicate of this issue

Added subscriber: @brecht

Added subscriber: @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.

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?

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.

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: 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! :)

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! :)

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.

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

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.

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.

Added subscriber: @jonbragado

Added subscriber: @jonbragado

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

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

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2019-06-25 18:40:26 +02:00

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: a4c907af77.

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

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: a4c907af77. I can reproduce the crash before that, but not anymore after.

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

Hi, Yes, It has been fixed by the recent update. Thanks for all the help and your time! :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#65921
No description provided.