Memory Leak creating new workspaces / move to collection (menu problem) #57098

New Issue

Antonio Vazquez · 2018-10-08T10:55:14+02:00

Antonio Vazquez commented

2018-10-08 10:55:14 +02:00

Windows 10 64 bits - Last source code compiled 08/10/2018 10:50 CET

To reproduce:

start blender with: blender --factory-startup --debug
Select default template with default cube.
Select in top tabs:General->Texture Paint
Close Blender

You get these memory leaks:

Error: Not freed memory blocks: 5, total unfreed memory 0.001175 MB
strdup len: 16 000001C5E973E068
strdup len: 12 000001C5E973E218
strdup len: 4 000001C5E97907B8
strdup len: 16 000001C5E973D2E8
mesh_render_data_create_ex len: 568 000001C5E555F248

Windows 10 64 bits - Last source code compiled 08/10/2018 10:50 CET To reproduce: 1) start blender with: **blender --factory-startup --debug** 2) Select default template with default cube. 3) Select in top tabs:**General->Texture Paint** 4) Close Blender You get these memory leaks: ``` Error: Not freed memory blocks: 5, total unfreed memory 0.001175 MB strdup len: 16 000001C5E973E068 strdup len: 12 000001C5E973E218 strdup len: 4 000001C5E97907B8 strdup len: 16 000001C5E973D2E8 mesh_render_data_create_ex len: 568 000001C5E555F248 ```

Antonio Vazquez commented

2018-10-08 10:55:15 +02:00

Added subscriber: @antoniov

Philipp Oeser commented

2018-10-10 09:41:20 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-10-10 09:41:20 +02:00

Not able to reproduce as of 84cf670d1d.
@antoniov : are you still getting the leaks now?

Not able to reproduce as of 84cf670d1d. @antoniov : are you still getting the leaks now?

Antonio Vazquez commented

2018-10-10 10:17:58 +02:00

@lichtwerk Yes, I still have the problem (compiled just now), but I have noticed something.

Start blender and in splash click in the splash image (load default scene)->No memory leak.

but, if you start blender, then select the template General, open texture paint tab and close->Memory leak.

The leak is only when use the default template, maybe it's something of the original template file, so not sure if we can close this bug.

@lichtwerk Yes, I still have the problem (compiled just now), but I have noticed something. Start blender and in splash click in the splash image (load default scene)->No memory leak. but, if you start blender, then select the template General, open texture paint tab and close->Memory leak. The leak is only when use the default template, maybe it's something of the original template file, so not sure if we can close this bug.

Antonio Vazquez commented

2018-10-10 10:23:01 +02:00

I have tested and the problem is with any template.

To reproduce:

Open Blender
Select any template
Open texture paint tab
Close Blender->Memory leak

I have tested and the problem is with any template. To reproduce: 1) Open Blender 2) Select any template 3) Open texture paint tab 4) Close Blender->Memory leak

Philipp Oeser commented

2018-10-10 10:56:26 +02:00

Hm, still cant reproduce.
Also resaved Userprefs/StartupFile, also made a new Template (with a TexturePaint workspace in it), still nothing...
(@antoniov: have an idea why its not leaking here?)

Does this happen with a fresh Template on your side as well (or if you move the default startup.blend and userpref.blend to a bak folder temporarily)?

Hm, still cant reproduce. Also resaved Userprefs/StartupFile, also made a new Template (with a TexturePaint workspace in it), still nothing... (@antoniov: have an idea why its not leaking here?) Does this happen with a fresh Template on your side as well (or if you move the default startup.blend and userpref.blend to a bak folder temporarily)?

Antonio Vazquez commented

2018-10-10 11:05:30 +02:00

It's very weird... I just downloaded the buildbolt version and tested and I get the problem too.

Are you in Windows 10?

I will try to investigate.

It's very weird... I just downloaded the buildbolt version and tested and I get the problem too. Are you in Windows 10? I will try to investigate.

Antonio Vazquez commented

2018-10-10 11:11:00 +02:00

What it's sure the problem is related to open new tabs... if I open 3 tabs, I have 3 times the memory leak.

I will try to make a debug this afternoon.

What it's sure the problem is related to open new tabs... if I open 3 tabs, I have 3 times the memory leak. I will try to make a debug this afternoon.

Philipp Oeser commented

2018-10-10 11:14:31 +02:00

Also tried the buildbot, still nothing. I'm on Linux though.

Philipp Oeser self-assigned this 2018-10-10 11:27:40 +02:00

Philipp Oeser commented

2018-10-10 11:27:40 +02:00

Ah, yes, get it now, too (that was a misunderstanding, I didnt understand that you meant creating a new workspace, I was just switching to them).
Also seems to be a difference between duplicating [right click on a workspace tab and choose "Duplicate" -- dont get the leak there] and creating a new [Plus icon and choosing one -- get the leak].

I can have a look.

Ah, yes, get it now, too (that was a misunderstanding, I didnt understand that you meant **creating a new workspace**, I was just switching to them). Also seems to be a difference between `duplicating` [right click on a workspace tab and choose "Duplicate" -- dont get the leak there] and `creating a new` [Plus icon and choosing one -- get the leak]. I can have a look.

Philipp Oeser commented

2018-10-10 15:52:05 +02:00

Added subscriber: @brecht

Philipp Oeser commented

2018-10-10 15:52:05 +02:00

note: Move To Collection menu also leaks ( propably all calls to uiItemMenuF [when called with an *arg] )
@brecht already commented (I think related?) here
Got to go, more tomorrow (check where to free again....)

note: `Move To Collection` menu also leaks ( propably all calls to uiItemMenuF [when called with an *arg] ) @brecht already commented (I think related?) [here ](https://developer.blender.org/diffusion/B/browse/blender2.8/source/blender/editors/screen/workspace_edit.c;074cbc403cb5498fddb1f963317fcd67b227c7c6$519) Got to go, more tomorrow (check where to free again....)

Philipp Oeser changed title from ~~Memory Leak using texture paint tab~~ to Memory Leak creating new workspaces / move to collection (menu problem)

2018-10-10 15:56:45 +02:00

Dalai Felinto commented

2018-10-10 16:28:43 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2018-10-10 16:28:43 +02:00

The move to collection is known if I remember correctly.
I would keep this report strictly to the workspace/texture paint issue.

In fact texture painting itself leaks a lot of memory here, depending on the mode. But I haven't stopped to investigate it though.

The move to collection is known if I remember correctly. I would keep this report strictly to the workspace/texture paint issue. In fact texture painting itself leaks a lot of memory here, depending on the mode. But I haven't stopped to investigate it though.

Philipp Oeser commented

2018-10-11 14:31:10 +02:00

tried my luck here and came up with D3783, seems to do the trick (even though there might be more elegant solutions...)

tried my luck here and came up with [D3783](https://archive.blender.org/developer/D3783), seems to do the trick (even though there might be more elegant solutions...)

Philipp Oeser commented

2018-10-30 16:07:23 +01:00

Original issue is fixed in 817319a79e, 5e091de0dc, still need to port this to the Move To Collection menu

Original issue is fixed in 817319a79e, 5e091de0dc, still need to port this to the `Move To Collection` menu

Philipp Oeser commented

2019-07-09 12:12:35 +02:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2019-07-09 12:12:35 +02:00

Philipp Oeser commented

2019-07-09 12:12:35 +02:00

This seems to be solved, closing...
Anyone: please kick me again if issues persist...

This seems to be solved, closing... Anyone: please kick me again if issues persist...

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

Memory Leak creating new workspaces / move to collection (menu problem) #57098