Crash when selecting force field #43713
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#43713
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 8.0 intel Hd 4600
Blender Version
Broken: 2.73.8
Worked: (optional)
Short description of error
when ever I try to select the force shield blender would crash
Exact steps for others to reproduce the error
https://drive.google.com/file/d/0B4CLCL8cP5lSYXZQbDlROXhwSHc/view?usp=sharing
select on of the force shields
Changed status to: 'Open'
Added subscriber: @Blendify
#48784 was marked as duplicate of this issue
Added subscriber: @JulianEisel
Can't recreate that here (Linux). First I'd say, do the normal things: Check drivers, use softwaregl, factory settings, check on other systems, etc. Also, you can paly a bit with the selection methods (UserPrefs->System->Selection). Then you could fire up your task manager to see how many percent of memory and cpu are used while you perform the selections. Selection is quite slow on my system as well, so maybe you're just running out of memory or so.
it is more of an immediate crash not lingering at high computer usage i tried to test with with opengl but it was to slow to process the ui and the vast amount stuff in the .blend
Added subscriber: @MartijnBerger
@MartijnBerger, any chance you can recreate this on Windows?
Added subscriber: @Sergey
I can't reproduce the issue with intel card on my windows 7 laptop.
The thing is, it's possible that the driver is doing crazy stuff and crashes, so: does the crash happen when you select force field frm the outliner?
Also, does it happen with more simple file?
Automatic
toOpenGL occlusion queries
did not crashOpenGL Select
crashedAdded subscriber: @Psy-Fi
So @Psy-Fi, let's blame drivers again?
Let's wait for a final test by reporter with tomorrow's testbuild, there was a fix for selection today.
I will have to test tomorrow i dont have access to my better computer today
still crashes
Changed status from 'Open' to: 'Archived'
Time to notify the Intel team, but will close here. https://software.intel.com/en-us/forums/topic/542235
what is the difference between the selection methods?
just so i know i wont be losing something by changing it to the one that did not crash
It's much faster, but sometimes you might not get the frontmost object, especially when two objects are near under your cursor.
ok not that bad of a trade off
Added subscriber: @fasano