API Image Operator bpy.ops.image.open - Segmentation Fault #53294

Closed
opened 2017-11-10 18:03:54 +01:00 by Mike · 12 comments

System Information
Kernel : Linux 4.10.0-38-lowlatency (x86_64)
Compiled : #42-Ubuntu SMP PREEMPT Tue Oct 10 14:33:03 UTC 2017
C Library : GNU C Library version (Ubuntu GLIBC 2.24-9ubuntu2.2) 2.24 (unstable)
Default C Compiler : GNU C Compiler version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
Distribution : Ubuntu 17.04
Graphics Card: Onboard

Blender Version
Broken:

  • blender-2.79-linux-glibc219-x86_64
  • blender-2.79-21a535840df-linux-glibc219-x86_64
    Worked:
  • blender-2.78c-linux-glibc219-x86_64

Short description of error
Segmentation fault when calling bpy API image operation "open" with any image file. This also cripples the NetRender addon.
bpy.ops.image.open(filepath=filename)

Exact steps for others to reproduce the error
I'm going to attach a sample python script that will cause the crash, in addition to a simple bash script that will use each of the three mentioned versions of blender, to show that only 2.78c official release works.

Attached here are the script files I used to reproduce the error

This is a simple bash script, which will call blender several times; Once per specified version. The release folder must be in the same folder if you want to actually use it.
cause-crash

This is the python script that fails on the two newer versions, but succeeds on official release 2.78c. It expects an input file called "test.exr" in the same directory, and will output "test.jpg" on success. I'm currently using it with an EXR generated by the NetRender addon. I can upload my test EXR I'm using if you like, but it also fails with any PNG I stick in there as well.
cause-crash.py

Here is output generated when I ran the script myself
log.txt

Here is the blender crash log generated from blender-2.79-21a535840df-linux-glibc219-x86_64
blender.crash.txt

**System Information** Kernel : Linux 4.10.0-38-lowlatency (x86_64) Compiled : #42-Ubuntu SMP PREEMPT Tue Oct 10 14:33:03 UTC 2017 C Library : GNU C Library version (Ubuntu GLIBC 2.24-9ubuntu2.2) 2.24 (unstable) Default C Compiler : GNU C Compiler version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) Distribution : Ubuntu 17.04 Graphics Card: Onboard **Blender Version** Broken: - blender-2.79-linux-glibc219-x86_64 - blender-2.79-21a535840df-linux-glibc219-x86_64 Worked: - blender-2.78c-linux-glibc219-x86_64 **Short description of error** Segmentation fault when calling bpy API image operation "open" with any image file. This also cripples the NetRender addon. bpy.ops.image.open(filepath=filename) **Exact steps for others to reproduce the error** I'm going to attach a sample python script that will cause the crash, in addition to a simple bash script that will use each of the three mentioned versions of blender, to show that only 2.78c official release works. Attached here are the script files I used to reproduce the error This is a simple bash script, which will call blender several times; Once per specified version. The release folder must be in the same folder if you want to actually use it. [cause-crash](https://archive.blender.org/developer/F1117914/cause-crash) This is the python script that fails on the two newer versions, but succeeds on official release 2.78c. It expects an input file called "test.exr" in the same directory, and will output "test.jpg" on success. I'm currently using it with an EXR generated by the NetRender addon. I can upload my test EXR I'm using if you like, but it also fails with any PNG I stick in there as well. [cause-crash.py](https://archive.blender.org/developer/F1117915/cause-crash.py) Here is output generated when I ran the script myself [log.txt](https://archive.blender.org/developer/F1117916/log.txt) Here is the blender crash log generated from blender-2.79-21a535840df-linux-glibc219-x86_64 [blender.crash.txt](https://archive.blender.org/developer/F1117917/blender.crash.txt)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @mikeperalta

Added subscriber: @mikeperalta

blender/blender#53446 was marked as duplicate of this issue

blender/blender#53446 was marked as duplicate of this issue
Author

This comment was removed by @mikeperalta

*This comment was removed by @mikeperalta*
Author

This comment was removed by @mikeperalta

*This comment was removed by @mikeperalta*
Author

This comment was removed by @mikeperalta

*This comment was removed by @mikeperalta*
Author

This comment was removed by @mikeperalta

*This comment was removed by @mikeperalta*

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This issue was referenced by blender/blender@5b3c15e336

This issue was referenced by blender/blender@5b3c15e3363aa7bea5d26c56191b7e8e74021868

Added subscribers: @meetar, @LazyDodo

Added subscribers: @meetar, @LazyDodo

Added subscriber: @ideasman42

Added subscriber: @ideasman42

note: better to use bpy.data.images.load

note: better to use `bpy.data.images.load`
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 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-addons#53294
No description provided.