fresh 2.83 compilation, immediate crash #73939
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#73939
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
Operating system: Linux-4.19.0-6-amd64-x86_64-with-debian-10.3 64 Bits
Graphics card: GeForce GTS 350M/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108 rev3
Blender Version
Blender 2.83 (sub 3), Commit date: 2020-02-17 10:16, Hash
cec7db2004
Worked: runs with no errors from command line with -b, or -h. Rendering works properly.
Short description of error
Hard crash after very fresh compilation (configured carefully with cmake-gui). Logs attached. NO idea what's wrong, I suspect GL system and legacy (yet updated) drivers. But 2.82 works (unstable).
debug.txt
blender.crash.txt
Xorg.0.log
Added subscriber: @piotao
Very similar behaviour to https://developer.blender.org/T70209 but none of workaround works.
Compilation of Blender 2.83 (sub 4), Commit date: 2020-02-17 19:54, Hash
00227edf4c
gives the same results.
Added subscriber: @ideasman42
This graphics card model (GForce-350m) is from around ~2010 (link )
Closing since this doesn't meet the system requirements of hardware under 10 years old.
See: https://www.blender.org/download/requirements/
If you're able to bisect the commit which caused this, it may be possible to support, however this cant be guaranteed.
Changed status from 'Needs Triage' to: 'Archived'
Thank you. I think it's better to look for a newer laptop. No real reason to looking back and hold the development. The only sad thing will be the losss of all nice stickers placed on laptop's lid gained during lots of Blender Conferences.
However, after a bit closer investigation, it seems that this crash is caused in the line which is not related to graphics at all. Just SIGSEGV due to some garbled pointer I believe. Here is gdb output.
Thread 1 "blender" received signal SIGSEGV, Segmentation fault.
0x0000555558f1d487 in GPU_draw_list_command_add ()
(gdb) backtrace
Please check this line:
list->cmd_len++;
from GPU_draw_list_command_add function in blender/source/blender/gpu/intern/gpu_batch.c
It seems that this is the cause of the crash. Therefore list is an invalid pointer. This is so far the result of my poor-man-investigation. I printed out the values which are passed to this function. They are:
list=0xc5cf6318, v_first=0, v_count=3, i_first=0, i_const=1
And the contents of list is the problem. Am I right?
Changed status from 'Archived' to: 'Needs Developer To Reproduce'
Added subscriber: @fclem
Thanks for looking into this.
There are some different code-paths for older hardware, for e.g.
USE_MULTI_DRAW_INDIRECT
is checked inGPU_draw_list_create
and other draw list API calls.If you are able, could you bisect this to find which commit broke this?
@fclem is this an issue you're aware of?
Thank you for support. I did bisect (multiple compilations took nearly a day).
I include bisect log.
However, I'm stuck at a strange revision which do not compile anymore! Compilation was successful from both ends - from 2.82 #77d23b0bd76 to latest 2.83 #e4605cb155b. But apparently something went terribly wrong, or maybe I have some unmet deps in this middle point, because compilation is no longer possible. I include compilation log from where it started to be noisy to the end when it broke.
Due to inability to compile this commit, I'm not sure I've found good bisect, however git was talking I'm one/two steps away at most.
And after git visualize, in gitk I spotted Clement's commits and this constant USE_MULTI_DRAW_INDIRECT somewhere. So we are close!
I'm not sure I included files correctly, where they go again:
bisect.log
compil.txt
My current git status is telling this:
Well, I've solved this issue using unusual brute force method: I've bought a new powerful laptop with RTX 2060. I hope this will live at least as long, as previous GTX350M.
However, I observe a very similar problem (the same error exactly) on our old computer laboratories which are equipped with GTX 260 cards, which have also OpenGL 3.3 (according to https://feedback.wildfiregames.com/report/opengl/device/GeForce%20GTX%20260). So, this will be very valuable to somehow manage Blender to work in this configuration. The error is even more annoying, because Blender 'works' for a minute or two, and then crashes. Usually this happens when new window has to be drawn, huge redraw of the screen area happens or shader compilation starts. The error has something with GLX errors and goes right from driver. Newer versions just do not work, causing crash mentioned above.
If you run into revisions which don't build while bisecting use
git bisect skip
.Changed status from 'Needs Developer To Reproduce' to: 'Archived'
I'm closing this one since this GPU is not supported anymore. However if anyone feels like picking it up feel free.
The thing that I would test is if just setting glew_arb_base_instance_is_supported to false fixes the issue. Also would be nice to know if the release version of blender (from the buildbot) does work.