GPv3: Memory leak when emptying a layer #118865

New Issue

Sietse Brouwer · 2024-02-28T20:37:07+01:00

Sietse Brouwer commented

2024-02-28 20:37:07 +01:00

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.61

Blender Version
Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-02-28 18:42, hash: 0e7c9f071a77

Short description of error
In GPv3, after emptying a layer (e.g. by deleting all strokes), Blender reports a memory leak when closing.

Exact steps for others to reproduce the error

Open a GPv3 document.
Draw some strokes.
Switch to Edit mode.
Select all strokes and delete them. The layer is empty now.
Close Blender.

Example of message when running blender.exe --debug-memory:

Error: Not freed memory blocks: 5, total unfreed memory 0.001884 MB
CDMIntProperty len: 8 000001FA067D57F0
make_implicit_sharing_info_for_layer len: 48 000001FA090EA350
customData_resize len: 640 000001FA2D2E6A28
customData_resize len: 640 000001FA2D2E5528
customData_resize len: 640 000001FA2D2E6428

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.61 **Blender Version** Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-02-28 18:42, hash: `0e7c9f071a77` **Short description of error** In GPv3, after emptying a layer (e.g. by deleting all strokes), Blender reports a memory leak when closing. **Exact steps for others to reproduce the error** - Open a GPv3 document. - Draw some strokes. - Switch to Edit mode. - Select all strokes and delete them. The layer is empty now. - Close Blender. Example of message when running `blender.exe --debug-memory`: ``` Error: Not freed memory blocks: 5, total unfreed memory 0.001884 MB CDMIntProperty len: 8 000001FA067D57F0 make_implicit_sharing_info_for_layer len: 48 000001FA090EA350 customData_resize len: 640 000001FA2D2E6A28 customData_resize len: 640 000001FA2D2E5528 customData_resize len: 640 000001FA2D2E6428 ```

Sietse Brouwer added the

labels 2024-02-28 20:37:08 +01:00

Pratik Borhade commented

2024-02-29 07:47:25 +01:00

Unable to confirm in current main b099108178038c8490d9c89a82cfa1afbafeccb5

Unable to confirm in current main `b099108178038c8490d9c89a82cfa1afbafeccb5`

Germano Cavalcante commented

2024-02-29 12:46:39 +01:00

I tested with the same version indicated: 0e7c9f071a77, but I was also unable to confirm the memory leak issue.
I followed these steps:

GPv3
New 2D Animation
Exit Draw Mode to add a new GP Object
Draw Mode
Draw some strokes
Edit Mode
Delete all strokes
Close Blender

Could you please provide more details in order to investigate further?
Check for any additional steps or specific conditions that could potentially trigger the memory leak.

I tested with the same version indicated: `0e7c9f071a77`, but I was also unable to confirm the memory leak issue. I followed these steps: - GPv3 - New 2D Animation - Exit Draw Mode to add a new GP Object - Draw Mode - Draw some strokes - Edit Mode - Delete all strokes - Close Blender Could you please provide more details in order to investigate further? Check for any additional steps or specific conditions that could potentially trigger the memory leak.

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-02-29 12:46:49 +01:00

Sietse Brouwer commented

2024-02-29 12:56:00 +01:00

Let's close the issue then. Probably some oddity in the Debug build. No need to chase ghosts!

Sietse Brouwer closed this issue

2024-02-29 12:56:03 +01:00