Blender Foundation: Blender 2.x BF release: Detail: 26501 Custom gui Checkboxes crash only in Linux 64 (32?)

Log In
New Account

[#26501] Custom gui Checkboxes crash only in Linux 64 (32?)

Date:
2011-03-14 19:17 Priority:
3

State:
Closed

Submitted by:
Juan Pablo Bouza (jpbouza) Assigned to:
Campbell Barton (campbellbarton)

Category:
OS related: Linux Status:
Fixed / Closed

Relates to: Duplicates:

Patches:

Summary:
Custom gui Checkboxes crash only in Linux 64 (32?)

Detailed description

rev 35499

Procedure:

1)Run the script provided in the blend file

2)A custom GUI will appear in VIEW3D

3)at the top right of the GUI there will appear some checkboxes called "all"

4) If you mouse over them or press them several times it will start doing odd things until blender crashes

Lines 89-91 define those buttons (I think), and they respond to the custom properties created in the armature panel (gui_hinge_all, gui_ik_all, gui_stretch_all)

I was able to make blender stop crashing though... What I did was to run the script, and then I edited it by commenting lines 89 to 91.
Then I ran the script again, and magically, the ALL buttons were still there, but they worked ok and they didn't crash!
Needless to say is that if you comment those lines without previously running the original script, the ALL buttons won't appear...

Followup

Message

Date: 2011-03-15 00:22
Sender: Campbell Barton
whats happening is every time you re-assign the UI properties the old ones are freed, but blender is still using them.

properties are supposed to be set on registering (or at least not while drawing), so disabled this in the API so it raises an exception.
You'll need to modify your script and move the property definitions out of draw().

Date: 2011-03-15 17:12
Sender: Juan Pablo Bouza
Campbell, but why does this work OK in windows and OSX and not in linux???

In windows and OSX it does not crash....

Date: 2011-03-16 00:42
Sender: Campbell Barton
On Win/OSX blender must be re-allocating the same memory regions often enough so access doesn't give a memory access crash.
Though on all OS's this is incorrect memory use and could easily crash if the memory allocator decided not to give those regions back to blender.

Attached Files:

Name	Date	Download

blenrig_bug.blend	2011-03-14 19:17	Download

Changes:

Field	Old Value	Date	By

status_id	Open	2011-03-15 00:22	campbellbarton
close_date	None	2011-03-15 00:22	campbellbarton
assigned_to	blendix	2011-03-15 00:22	campbellbarton
Status	Investigate	2011-03-15 00:22	campbellbarton
assigned_to	none	2011-03-14 19:18	ton
Status	New	2011-03-14 19:18	ton
File Added	15405: blenrig_bug.blend	2011-03-14 19:17	jpbouza