eGPU 2.80 - Blender crashes while moving area lights in edit mode using eGPU on internal display. #62234
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#62234
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?
Added subscriber: @mix1189
Additional Info:
Additional Info:
Added subscriber: @brecht
Please use the bug reporting template and provide all the requested information:
https://developer.blender.org/maniphest/task/edit/form/1/
Particularly a .blend file and exact steps to reproduce the problem.
Hi @brecht, sure thing!
System Information
Operating system: Mac OS Mojave 10.14.3
Graphics card:
Blender Version
Broken: 2.80 (
a070815d12
) March 07, 00:08:27Short description of error
Blender crashes every time immediately after selecting, moving or editing Area / Spot Lights when the application is used on the internal Macbook Displaywhile the latter is connected to an eGPU (via the Razer Core X, Thunderbolt 3) and an external monitor. The crash every time on empty files as well as simple scenes no matter what is the view mode.
NOTE: The crash doesn't happen if Blender is used on the external display, but happen every time the Blender window is moved into the macbook internal display (following the steps below).
Exact steps for others to reproduce the error
OPTION 1:
OPTION 2:
File Attached (But the problem persist on empty scenes too)
broom-2 copy.blend
Added subscriber: @Blendify
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
Is this still an issue with blender 2.82?
Changed status from 'Needs User Info' to: 'Archived'
No reply so far, given that this was reported on a beta version of 2.80 assuming this has been solved. If it can be confirmed in the latest build, we can reopen the issue.
Hi @brecht
sorry for the late reply here. I ran some test yesterday and looks like the issue has been solved!
Great, thanks for testing.