Repeated hiding and unhiding of objects causes more memory usage #59525

Closed
opened 2018-12-18 01:42:26 +01:00 by Sam Van Hulle · 8 comments

System Information
Operating system: Windows
Graphics card: GTX 960

Blender Version
Broken: 2.80 9149e894210

Short description of error
Repeated hiding and unhiding of objects causes Blender's total memory usage to rise. Higher numbers of objects (presumably also polycounts) have a larger impact.

Exact steps for others to reproduce the error
Repeatedly hide and unhide any number of objects in the viewport - I used the eye icon in the Outliner.

**System Information** Operating system: Windows Graphics card: GTX 960 **Blender Version** Broken: 2.80 `9149e894210` **Short description of error** Repeated hiding and unhiding of objects causes Blender's total memory usage to rise. Higher numbers of objects (presumably also polycounts) have a larger impact. **Exact steps for others to reproduce the error** Repeatedly hide and unhide any number of objects in the viewport - I used the eye icon in the Outliner.
Author

Added subscriber: @frameshift

Added subscriber: @frameshift

Added subscriber: @ideasman42

Added subscriber: @ideasman42

This adds undo steps which use memory, unless the memory usage increased significantly since 2.7x it's not a bug.

This adds undo steps which use memory, unless the memory usage increased significantly since 2.7x it's not a bug.
Author

Fair enough, makes sense.
Is it normal though for undo steps to take up more memory when the complexity of said objects increases? Even if the datablocks are linked from another library?
A cube, for example, adds kilobytes. A forest of linked trees adds tens of megabytes each time.

Fair enough, makes sense. Is it normal though for undo steps to take up more memory when the complexity of said objects increases? Even if the datablocks are linked from another library? A cube, for example, adds kilobytes. A forest of linked trees adds tens of megabytes each time.

Added subscriber: @ZedDB

Added subscriber: @ZedDB

IIRC, the undo system save snapshots of the scene data (not diffs). So the more complex objects will add more to memory, yes.

IIRC, the undo system save snapshots of the scene data (not diffs). So the more complex objects will add more to memory, yes.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Campbell Barton self-assigned this 2018-12-19 23:55:09 +01:00

Right, there are snapshots but only changed chunks of memory are stored.

Did a quick comparison and it seems this isn't working especially differently in 2.8x compared to 2.7x. Closing.

@frameshift - if you can show an example where this is significantly worse in 2.8x compared to 2.79 release. Open a new report with sample file.

Right, there are snapshots but only changed chunks of memory are stored. Did a quick comparison and it seems this isn't working especially differently in 2.8x compared to 2.7x. Closing. @frameshift - if you can show an example where this is significantly worse in 2.8x compared to 2.79 release. Open a new report with sample file.
Sign in to join this conversation.
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: studio/blender-studio#59525
No description provided.