Blender 2.80 - Crash when resizing region #62933
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#62933
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
OS: Ubuntu 18.04.2 LTS
Kernel: Linux 4.15.0-46-generic
Graphics card: AMD RX 480
driver: amdgpu-pro - 18.40-676022
resolution: 1366x768
Blender Version
Broken:
Blender 2.80
Date: 2019-03-24 22:08
Hash:72ede30d0f97
Branch: blender2.7
Short description of error
Blender crashed when resizing the viewport region while repeating the experiment from my other report #62931: https://streamable.com/kzlwt, but this time from a new fresh file. Just resizing the region back and forth, and releasing the click and continuing doing so multiple times crashed Blender
console log after crash:
GPUTexture: create : TEXTURE_2D, RGBA8, w : 456, h : 295, d : 0, comp : 4, size : 0.51 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.51 MiB.
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)
Exact steps for others to reproduce the error
1 - File > New > General
2 - Select "Shading" tab
3 - Select LookDev mode as display
3 - Resize the viewport region back and forth horizontally, release and continue resizing multiple times
blender.crash.txt
Added subscriber: @mikewazowski11
Added subscriber: @ZedDB
As in the other report, check if this still happens with the latest drivers.
I installed the latest version of AMD gpupro driver: amdgpu-pro 18.50-725072, and I am still able to reproduce the crash.
Unable to reproduce. Could you add the
systeminfo.txtto this report. Also could you start blender with./blender --debug-value 21and make a recording together with a system memory profiler.Also perform the same task with
--debug-gpuand add the console log to this ticket.With a "recording", do you mean a screen recording? please elaborate this.
And with the "system memory profiler" part, will the System Monitor of Ubuntu do the job?, or do I need another tool?
@mikewazowski11 Could you check if you can still reproduce this issue with the build of tomorrow. I did a related fix today. But just better to be sure this is fixed also before closing.
Added subscriber: @Mets
Changed status from 'Open' to: 'Resolved'
No update in a while so I'll close if that's alright. @mikewazowski11 if you could confirm that you no longer crash on the latest build that'd be great!
@Mets I tried for a while but couldn't reproduce the issue so far, thanks!