Long response time on objects at collection or object view disabling or entering edit mode #76809

Closed
opened 2020-05-16 19:02:45 +02:00 by Grzegorz Radomski · 8 comments

{F8538983}System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87
Intel Core i7-5820K 3.3Ghz

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4ca
Worked: (optional)

Short description of error
[On my file i have two object. One is created from particle system and metaballs - converted to mesh (~99K). Object have Subdiv. modifier. When i press Tab to edit, blender seams freeze for about 15-20 s. after this i could edit model. Same when i want exit edit mode. When i apply subdiv modifier everything work correctly. Another cases is when i want unhide collection or object with this model (by pressing disable in view icon) or switching on/off subdivsion modifier blender need this 15-20 s. to complete action.

In scene i put another object. This is a model of the cap also with subdivision. Entering edit mode work good but unhiding collection or object (by pressing disable in view icon) work with same problems like first one.

I test this scene in 2.82, 2.81, 2.80 and have same result. I haven't this problem (entering edit mode) on version 2.79.

Another problem i have with object-1 is when i export him using obj format i couldn't import correctly to 2.79 version. Format fbx let me import this model to older version.
Maybe it's another bug but could be somehow connected.

Thanks for Your great work
]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

{[F8538983](https://archive.blender.org/developer/F8538983/Blender-long-response.zip)}**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87 Intel Core i7-5820K 3.3Ghz **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `375c7dc4ca` Worked: (optional) **Short description of error** [On my file i have two object. One is created from particle system and metaballs - converted to mesh (~99K). Object have Subdiv. modifier. When i press Tab to edit, blender seams freeze for about 15-20 s. after this i could edit model. Same when i want exit edit mode. When i apply subdiv modifier everything work correctly. Another cases is when i want unhide collection or object with this model (by pressing disable in view icon) or switching on/off subdivsion modifier blender need this 15-20 s. to complete action. In scene i put another object. This is a model of the cap also with subdivision. Entering edit mode work good but unhiding collection or object (by pressing disable in view icon) work with same problems like first one. I test this scene in 2.82, 2.81, 2.80 and have same result. I haven't this problem (entering edit mode) on version 2.79. Another problem i have with object-1 is when i export him using obj format i couldn't import correctly to 2.79 version. Format fbx let me import this model to older version. Maybe it's another bug but could be somehow connected. Thanks for Your great work ] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]

Added subscriber: @rad-sky

Added subscriber: @rad-sky
Member

Added subscriber: @Calra

Added subscriber: @Calra
Member

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

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

@rad-sky Could you fill in the exact steps on how to reproduce the error, they are vaguely there in the description still more precise ones, in bullet format, like step1,- Do this, step 2 -Go there, Step 3 and so on? It would make fixing the bug easier.

Thanks !

@rad-sky Could you fill in the exact steps on how to reproduce the error, they are vaguely there in the description still more precise ones, in bullet format, like step1,- Do this, step 2 -Go there, Step 3 and so on? It would make fixing the bug easier. Thanks !

Exact steps for others to reproduce the error

Case 1 (long time entering edit mode)

  1. select Mball.001 object
  2. press Tab to enter edit mode
  3. press Tab to exit edit mode

Case 2 (long time hiding object by pressing disable in viewport icon > Outliner)

  1. press disable in viewport icon on object Mball.001 or on cap object
    (pressing eye icon to hide/unhide works normally)

PS.
another symptom scene with those objects loading longer when opening file.

Exact steps for others to reproduce the error Case 1 (long time entering edit mode) 1. select Mball.001 object 2. press Tab to enter edit mode 3. press Tab to exit edit mode Case 2 (long time hiding object by pressing disable in viewport icon > Outliner) 1. press disable in viewport icon on object Mball.001 or on cap object (pressing eye icon to hide/unhide works normally) PS. another symptom scene with those objects loading longer when opening file.
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

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

Changed status from 'Needs User Info' to: 'Archived'
Ankit Meel self-assigned this 2020-05-17 11:34:42 +02:00
Member

image.png
In case 1, when the drop happened, I had pressed tab. so a lot of memory was freed, and then refilled.
You may follow the discussion at #74186 (Proposal for fast high poly mesh editing).
Thanks for the report, but performance issues are not considered as bug on the tracker.
Simpler geometry, shading etc can be used to avoid lag.

![image.png](https://archive.blender.org/developer/F8539857/image.png) In case 1, when the drop happened, I had pressed tab. so a lot of memory was freed, and then refilled. You may follow the discussion at #74186 (Proposal for fast high poly mesh editing). Thanks for the report, but performance issues are not considered as bug on the tracker. Simpler geometry, shading etc can be used to avoid lag.
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#76809
No description provided.