Change between modes up ram consumption, multres modifier. #94474

New Issue

Higor Moura · 2021-12-29T23:58:31+01:00

Higor Moura commented

2021-12-29 23:58:31 +01:00

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76

Blender Version
Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca30557
Worked: (newest version of Blender that worked as expected)

Short description of error
[Change modes edit to object and repeat, up ram consume, with multresolution modifier with 5 subd.]

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)]

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `f1cca30557` Worked: (newest version of Blender that worked as expected) **Short description of error** [Change modes edit to object and repeat, up ram consume, with multresolution modifier with 5 subd.] **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)]

Higor Moura commented

2021-12-29 23:58:31 +01:00

Added subscriber: @visturine

Fen commented

2021-12-30 02:50:07 +01:00

Added subscriber: @chemicalcrux

Fen commented

2021-12-30 02:50:07 +01:00

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

Fen commented

2021-12-30 02:50:07 +01:00

I spawned a Monkey object, added a Multiresolution modifier, and used it to subdivide five times. I then switched between edit and object mode a few dozen times. I saw a modest increase at first on MacOS, but it didn't grow forever.

Is it going up until you completely run out of memory?

I spawned a Monkey object, added a Multiresolution modifier, and used it to subdivide five times. I then switched between edit and object mode a few dozen times. I saw a modest increase at first on MacOS, but it didn't grow forever. Is it going up until you completely run out of memory?

Higor Moura self-assigned this 2021-12-30 12:47:05 +01:00

Higor Moura commented

2021-12-30 12:47:05 +01:00

{F12781764}Yes, it keeps going up until the blender breaks, or, totally overloads my ram.

{[F12781764](https://archive.blender.org/developer/F12781764/Blender__C__Users_vistu_OneDrive_Documentos_Trabalhos_Pedro_Raimundo_RaimundoHighRetopoMultres.blend__2021-12-30_08-38-39.mp4)}Yes, it keeps going up until the blender breaks, or, totally overloads my ram.

Michael commented

2021-12-30 17:34:40 +01:00

Added subscriber: @michael64

Michael commented

2021-12-30 17:34:40 +01:00

I have run this situation on macOS with Apple M1 in the memory leaks instrument of Xcode. This shows the current memory allocations graphically.
If I slowly tab between object and edit mode every 5 seconds the memory allocations go up and down but the upper memory allocation limit is not increasing.
When I hammer the tab key very quickly the total memory allocations go up and up and up.

Looking up where these additional memory allocations come from showed this call stack:

0 Blender MEM_lockfree_dupallocN
1 Blender layerCopy_mdisps(void const*, void*, int)
2 Blender CustomData_from_bmesh_block
3 Blender BM_mesh_bm_to_me
4 Blender mesh_undosys_step_encode
5 Blender BKE_undosys_step_push_with_type
6 Blender ED_undo_push
7 Blender wm_operator_finished
8 Blender wm_operator_invoke
9 Blender wm_operator_call_internal
10 Blender ED_object_mode_set_ex
11 Blender object_mode_set_exec
12 Blender wm_operator_invoke
13 Blender wm_handler_operator_call

So it seems that the undo system is allocating 3584 bytes of memory each time tab is pressed which even might be ok.

I have run this situation on macOS with Apple M1 in the memory leaks instrument of Xcode. This shows the current memory allocations graphically. If I slowly tab between object and edit mode every 5 seconds the memory allocations go up and down but the upper memory allocation limit is not increasing. When I hammer the tab key very quickly the total memory allocations go up and up and up. Looking up where these additional memory allocations come from showed this call stack: 0 Blender MEM_lockfree_dupallocN 1 Blender layerCopy_mdisps(void const*, void*, int) 2 Blender CustomData_from_bmesh_block 3 Blender BM_mesh_bm_to_me 4 Blender mesh_undosys_step_encode 5 Blender BKE_undosys_step_push_with_type 6 Blender ED_undo_push 7 Blender wm_operator_finished 8 Blender wm_operator_invoke 9 Blender wm_operator_call_internal 10 Blender ED_object_mode_set_ex 11 Blender object_mode_set_exec 12 Blender wm_operator_invoke 13 Blender wm_handler_operator_call So it seems that the undo system is allocating 3584 bytes of memory each time tab is pressed which even might be ok.

Pratik Borhade commented

2022-04-27 08:10:59 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-04-27 08:10:59 +02:00

Thanks for the report. This issue has been already reported here: #88010 (Memory consumption beyond defined limit when entering-exiting Edit mode)
Will merge this report

Thanks for the report. This issue has been already reported here: #88010 (Memory consumption beyond defined limit when entering-exiting Edit mode) Will merge this report

Pratik Borhade commented

2022-04-27 08:11:18 +02:00

Closed as duplicate of #88010

Pratik Borhade closed this issue

2022-04-27 08:11:18 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Change between modes up ram consumption, multres modifier. #94474