BVHTree object is not dealloced when using global operator in code. #47556

New Issue

Germano Cavalcante · 2016-02-24T18:29:43+01:00

2016-02-24 18:29:43 +01:00

System Information
Windows 64bits

Blender Version
Broken: 2.76

Short description of error
When you have finished running a python code with a BVHTree object, it is expected that it's tree has been released at the end of the code and not when close Blender. Unfortunately the object is not dealloced when the code has the "global" operator anywhere
.
Exact steps for others to reproduce the error
run this code:

import bpy
from mathutils import bvhtree
print("-------------------------------")

gl = None
def get_global_gl():
    global gl
    return gl

obj = bpy.context.object
scene = bpy.context.scene

tridata = bvhtree.BVHTree.FromObject(obj, scene)
#del tridata

And make sure that the BVHTree object has been dealloced (I put a printf in the source code).

**System Information** Windows 64bits **Blender Version** Broken: 2.76 **Short description of error** When you have finished running a python code with a BVHTree object, it is expected that it's tree has been released at the end of the code and not when close Blender. Unfortunately the object is not dealloced when the code has the "global" operator anywhere . **Exact steps for others to reproduce the error** run this code: ``` import bpy from mathutils import bvhtree print("-------------------------------") gl = None def get_global_gl(): global gl return gl obj = bpy.context.object scene = bpy.context.scene tridata = bvhtree.BVHTree.FromObject(obj, scene) #del tridata ``` And make sure that the BVHTree object has been dealloced (I put a printf in the source code).

Germano Cavalcante commented

2016-02-24 18:29:43 +01:00

Changed status to: 'Open'

Germano Cavalcante commented

2016-02-24 18:29:43 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2016-02-24 18:47:19 +01:00

EDIT: Does not even need the "global" statement, only a function is enough.

NikoLeopold commented

2016-02-25 04:12:35 +01:00

Added subscriber: @NikoLeopold

Sergey Sharybin commented

2016-02-25 10:39:05 +01:00

Added subscribers: @ideasman42, @Sergey

Campbell Barton was assigned by Sergey Sharybin

2016-02-25 10:39:05 +01:00

Sergey Sharybin commented

2016-02-25 10:39:05 +01:00

@ideasman42, not sure it's supposed to be freed that way actually, mind having a look?

Campbell Barton commented

2016-02-25 11:11:07 +01:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2016-02-25 11:11:07 +01:00

Campbell Barton commented

2016-02-25 11:11:07 +01:00

This is Python's GC - known behavior.

If we want we could do a gc.collect() before exiting which resolves most cases, but not sure its really worth it since this is known CPython behavior and only going to make exit slower for something which is harmless and only a bit confusing when debugging. see: http://stackoverflow.com/questions/14628486

We could run gc.collect() with debug builds, or check the --debug-python flag.

This is Python's GC - known behavior. If we want we could do a `gc.collect()` before exiting which resolves most cases, but not sure its really worth it since this is known CPython behavior and only going to make exit slower for something which is harmless and only a bit confusing when debugging. see: http://stackoverflow.com/questions/14628486 We could run gc.collect() with debug builds, or check the `--debug-python` flag.

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

BVHTree object is not dealloced when using global operator in code. #47556