Crash after resizing window to split the screen in half #95792

Closed
opened 2022-02-15 03:10:28 +01:00 by Davide · 8 comments

{F12867753}System Information
Operating system: Windows 11
Graphics card: Nvidia GeForce RTX 3060 (laptop)

Blender Version
3.0.1

Short description of error
The program crashed after resizing the window

Exact steps for others to reproduce the error
The program crashed as it is seen in the videoclip I uploaded

{[F12867753](https://archive.blender.org/developer/F12867753/Blender_crash.mp4)}**System Information** Operating system: Windows 11 Graphics card: Nvidia GeForce RTX 3060 (laptop) **Blender Version** 3.0.1 **Short description of error** The program crashed after resizing the window **Exact steps for others to reproduce the error** The program crashed as it is seen in the videoclip I uploaded
Author

Added subscriber: @DavideFraccaro

Added subscriber: @DavideFraccaro
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Thanks for the report. Can not get the crash on 3.0.1 (neither on current master)
I assume steps to get the crash are: split screen then open running blender instance on other side.
Does this happen when particular file is open?
Do you have multiple monitor setup?
Can you provide crash logs generated after the crash?:
Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).{[F8190038](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)}

Thanks for the report. Can not get the crash on 3.0.1 (neither on current master) I assume steps to get the crash are: split screen then open running blender instance on other side. Does this happen when particular file is open? Do you have multiple monitor setup? Can you provide crash logs generated after the crash?: ```Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).{[F8190038](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)}```
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

@Harley , are you able to reproduce? Otherwise I'll close this report (over a week without activity)
I couldn't get any crash with steps shown in the video.
neither crashes when I tested this on Secondary monitor

@Harley , are you able to reproduce? Otherwise I'll close this report (over a week without activity) I couldn't get any crash with steps shown in the video. neither crashes when I tested this on Secondary monitor
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Member

More than a week without reply. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

More than a week without reply. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
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
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#95792
No description provided.