OSL crash on 32bit #48542
Labels
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#48542
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 7 64 bit
Intel Core2 Quad Q9300; 4,0 GB RAM
GeForce GTX 460; driver: 361.75
Blender Version
Broken:
abf6f08
win323ed2b11
win32cd4d80f
win32Worked:
f337fea
win32;cd4d80f
win64Short description of error
If "Open Shading Language" is activated and Blender is in Cycles render mode, Blender will crash on win32 builds after 2.76b.
Exact steps for others to reproduce the error
Changed status to: 'Open'
Added subscriber: @hg1
#48778 was marked as duplicate of this issue
Added subscriber: @ThomasDinges
Why are you using a 32bit build on a x64bit OS?
Also make sure your OS us fully up to date (latest Service pack and updates).
Why not?
I don't know if there any speed improvements for Cycles (using Cuda) or Blender render engine but normally I don't use it, so I don't care.
So there is no benefits by using the 64 bit version for me.
My last Windows update is form 06.03.2016
I will check for new updates and will report afterwards.
Added subscribers: @MartijnBerger, @mont29
All those reasons are not very good to use 32bit on 64bit platform (« Mostly I use the BGE and the 64 bit version has more bugs » seriously? I’d like to know what’s broken on 64bit that works on 32bit…) - but there is absolutely no reason for 32bit builds to fail in 64bit windows!
We need some windows dev here, @MartijnBerger maybe you can try to reproduce?
OSL crash after activationto OSL crash after activation (using 32bit blender on 64bit windows)I wouldn't consider this a valid bug though.
64 bit Blender failing on 64 bit OS, ok.
32 bit Blender failing on 32 bit OS, ok.
But in this combination, I wouldn't spend much energy on trying to find whats wrong.
I have updated windows and the graphic card driver. As expected still crashing.
For me that are enough reasons. A specially that the 32 bit python libraries are not working with python 64 bit. Also I don't see an reason to use a 64 bit version. Or can you tell me one good reason why I should use it.
Most of the bugs are related with the Bullet and constraints. Most of them are fixed now by Sybren A. Stüvel, Porteries Tristan and me. Actually I know that there is a Bullet heap fault which sometimes let the BGE crash.
seriously? You want to leave this bug?
Also do you have tested 32 bit Blender with 32 bit OS?
I don't have Windows and I don't have a 32bit OS. If someone can reproduce the issue with the two combinations I mentioned above, then I will leave this open. Otherwise I will close it. It's just not a practical combination. You can also not run a 32bit Blender on a 64bit OS and use CUDA, that will not work either.
Lol you want to close an obviously bug the will crash Blender. When I have time I will test it on one of the lab PC's with 32 bit Windows 7.
No, running a 32 bit software on 64 bit OS is normal combination should also work.
No, that is definitely not correct. CUDA works with this combination.
I can confirm the crash on Ubuntu x64, with Blender 2.77a (32bit binary). 64bit binary is fine.
OSL is a third party library, we updated it for 2.77, maybe that's the reason for the crash. We are one of the few (if not the only) program that still supports OSL on 32bit. VRAY, Appleseed...other renderers with OSL support are 64bit only. I wouldn't be surprised if there are simply issues in the library on 32bit, because no one uses that ancient stuff anymore...
Added subscriber: @LazyDodo
Looks like OSL is getting unhappy , I don't have debugging symbols for the libs in svn so can't debug this further (and don't have the time to build my own libs right now)
Line causing the exception:
https://git.blender.org/gitweb/gitweb.cgi/blender.git/blob/HEAD:/intern/cycles/kernel/osl/osl_shader.cpp#l394
Callstack:
Given it's trying to write to address 0x00000002 it kinda looks like a null-deref in osl?
I just tested 2.77a and lastest nightly on a 32 bit host, they crash as well , also this is not limited to viewport renders, just enabling osl and doing a render will take down the process as well.
I can confirm the crash on windows 7 32 bit.
I grabbed the latest OSL from git which didn't crash anymore, bisected it until i found the commit that fixed it
7aa83e4dbc
We can easily patch this in our libs in svn for windows, however that doesn't quite help linux users
Wait for a new upstream release?
I think we can ask Larry to backport this to the OSL 1.7.x branch and just update libs then. Thanks for checking!
Added subscriber: @Sergey
@ThomasDinges, it is really rare case when 32bit application will crash on 64bit OS and will not crash on 32bit. It totally worth investigaiton.
@LazyDodo, this is a good find, but commit message does not mention anything about what and it was changed and whether it fixes anything. and why would that code run fine on 64bit and fail on 32bit? And why wouldn't that issue re-appear in the future?
What i mean is, it totally worth checking with OSL guys if it's a legit fix or just co-incidence which happened to fix our issue.
@ThomasDinges, are you in contact with Larry about this?
I am not in contact with Larry about this, will leave this to someone else. :)
Added subscriber: @brecht
The fix for this was committed in the OSL RB-1.7 branch:
f93f04c823
The remaining work here then is to rebuild the 32 bit OSL libraries on Windows and Linux, and update
install_deps.sh
.Actually this bit is wrong, this bug affects all 32 bit builds, not just the ones running on x64.
Messing up the calling convention will do that , not an issue on code build for x64 cause x64 ignores fastcall (at-least on msvc can't say for sure how gcc handles this) and uses 'standard' calling convention.
It seemed deliberate but you're right the commit is a bit sparse on why they made this change or what bug they were solving.
Brecht seems to have had contact with them?
There was talk of a 2.77b build during last meeting, this is probably one that we should include if we were to do 2.77b
OSL crash after activation (using 32bit blender on 64bit windows)to OSL crash after activation on 32bit windowsI updated install_depsh.sh, to use the new OSL 1.7.3. System libraries for Windows and Mac still need to be updated.
New title is wrong, this affects ALL 32 bit builds, inc linux.
OSL crash after activation on 32bit windowsto OSL crash on 32bitAdded subscriber: @lpjunior999
Changed status from 'Open' to: 'Resolved'
I've updated crucial platforms for this issue and poked buildbot to deliver new builds.
There are still some missing updates, but those platforms are 64bit only, so does not affect this issue.
Thanks for the report and investigation, closing it now!