not freed memory blocks on regular exiting #48027

New Issue

Norbert Krieg · 2016-04-01T12:11:15+02:00

Norbert Krieg commented

2016-04-01 12:11:15 +02:00

System Information
Linux 64 Debian Jessie - NVidia GTX 660 Ti

Blender Version
Broken: 2.77 (release), 2.76b

Short description of error
after quitting a fresh installation of the actual blender release via Ctrl-Q
an error occurs in the command line:

...
Error: Not freed memory blocks: 2, total unfreed memory 0.000732 MB

Blender quit

Exact steps for others to reproduce the error
with a fresh installation, without copying earlier setups

call freshly installed blender from release download
save user settings (to produce the 2.77 folder and subfolders etc)
exit blender
call blender
exit via Ctrl-Q

Error: Not freed memory blocks: 2, total unfreed memory 0.000732 MB

call blender
quit blender via closing window button of OS

no error
Funny....
Probably some different treatment of the quitting processes... ??

**System Information** Linux 64 Debian Jessie - NVidia GTX 660 Ti **Blender Version** Broken: 2.77 (release), 2.76b **Short description of error** after quitting a fresh installation of the actual blender release via Ctrl-Q an error occurs in the command line: > ... > Error: Not freed memory blocks: 2, total unfreed memory 0.000732 MB > > Blender quit **Exact steps for others to reproduce the error** with a fresh installation, without copying earlier setups 1. call freshly installed blender from release download 2. save user settings (to produce the 2.77 folder and subfolders etc) 3. exit blender 4. call blender 5. exit via Ctrl-Q - > Error: Not freed memory blocks: 2, total unfreed memory 0.000732 MB 6. call blender 7. quit blender via closing window button of OS - > no error Funny.... Probably some different treatment of the quitting processes... ??

Norbert Krieg commented

2016-04-01 12:11:15 +02:00

Changed status to: 'Open'

Norbert Krieg commented

2016-04-01 12:11:15 +02:00

Added subscriber: @nobi08

Bastien Montagne commented

2016-04-01 12:15:45 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2016-04-01 12:15:45 +02:00

This needs a win dev to check… probably some missing memfree in specific windows quit handling?

Campbell Barton commented

2016-04-04 11:26:19 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-04-04 11:26:19 +02:00

Can't redo this bug.
Tested on Windows7, official 2.77 release and master (d91316dc67)

Can't redo this bug. Tested on Windows7, official 2.77 release and master (d91316dc672dc1ee69fbd24d2f00124a24b75c6b)

perfection cat commented

2016-04-05 07:45:39 +02:00

Added subscriber: @sindra1961

perfection cat commented

2016-04-05 07:45:39 +02:00

When I confirmed a report #48057 , it occurred only once.
I ran blender with --factory-startup option.

Windows 10 Pro 64bits
Blender version: 2.77 (sub 0), commit date: 2016-04-04 23:20, hash: 9c952bb

When I confirmed a report [#48057 ](https://developer.blender.org/T48057), it occurred only once. I ran blender with --factory-startup option. Windows 10 Pro 64bits Blender version: 2.77 (sub 0), commit date: 2016-04-04 23:20, hash: 9c952bb

Ray molenkamp commented

2016-12-07 03:38:17 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2016-12-07 03:38:17 +01:00

I'm also unsuccessful full in reproducing this one. Why is this tagged windows? original report came in on Linux 64 Debian Jessie ?

Vuk Gardašević commented

2016-12-07 05:22:04 +01:00

Added subscriber: @VukGardasevic

Vuk Gardašević commented

2016-12-07 05:22:04 +01:00

I've reproduced the bug on several builds from 2.57 to recent ones.

Run Blender with -d --factory-startup go directly to the File > Quit menu.

Accessing it from the Ctrl + Q shortcut doesn't cause the leak.

memory_leak732.txt

Win 7 64 bit.

I've reproduced the bug on several builds from 2.57 to recent ones. Run Blender with ` -d --factory-startup` go directly to the `File > Quit` menu. Accessing it from the Ctrl + Q shortcut doesn't cause the leak. [memory_leak732.txt](https://archive.blender.org/developer/F415170/memory_leak732.txt) Win 7 64 bit.

Julian Eisel commented

2017-02-13 14:39:42 +01:00

Added subscriber: @JulianEisel

Julian Eisel self-assigned this 2017-02-13 14:39:42 +01:00

Julian Eisel commented

2017-02-13 14:39:42 +01:00

Can easily recreate this using steps mentioned by @lijenstina.

Vuk Gardašević commented

2017-12-11 15:54:23 +01:00

Note: after some further testing related to a bug report, setting the operator_context in the space_info.py to EXEC_AREA causes the issue. If a confirmation pop-up is called, there is no memory leak.

        layout.operator_context = 'EXEC_AREA'
        if bpy.data.is_dirty and context.user_preferences.view.use_quit_dialog:
            layout.operator_context = 'INVOKE_SCREEN'  # quit dialog

Note: after some further testing related to a bug report, setting the operator_context in the `space_info.py` to **EXEC_AREA** causes the issue. If a confirmation pop-up is called, there is no memory leak. ``` layout.operator_context = 'EXEC_AREA' if bpy.data.is_dirty and context.user_preferences.view.use_quit_dialog: layout.operator_context = 'INVOKE_SCREEN' # quit dialog ```

blender-admin commented

2018-03-22 23:09:19 +01:00

This issue was referenced by 4cb4556fa5

This issue was referenced by 4cb4556fa5ba78fff69cf2f6cb1d156d1705a5c5

Julian Eisel commented

2018-03-22 23:36:40 +01:00

Changed status from 'Open' to: 'Resolved'

Julian Eisel closed this issue

2018-03-22 23:36:40 +01: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

not freed memory blocks on regular exiting #48027