Calling bpy.ops.screen.screen_full_area() multiple times in python console causes Blender to crash #43139

New Issue

jon denning · 2015-01-05T22:24:27+01:00

jon denning commented

2015-01-05 22:24:27 +01:00

System Information
Linux jdenning-Notebook 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Intel Corp Haswell-ULT Integrated Graphics Controller

Blender Version
Broken: 2.73 273fa0a on Linux and dcc5997 on Mac
Worked: 2.73 fdddd4e on Windows 64

Short description of error

Calling bpy.ops.screen.screen_full_area() multiple times in python console causes Blender to crash. Note: calling the first time returns {'FINISHED'}, but the second time (switching away from full-area mode) does not return anything. In fact, except for coming out of full-area mode, the console acts as if it didn't execute anything.

Exact steps for others to reproduce the error

Open the standard/default start-up .blend file (with info, 3D view, outliner, properties, timeline).
Change timeline area to Python console.
Type bpy.ops.screen.screen_full_area() and press enter. (console now takes up full window)
Press up arrow then enter to call function again. (Note that the line is still there)
Press enter to call the function again. (no need to press up!)
Repeat last two steps multiple times will cause Blender to crash after 1 to many times, usually within 10 calls.

Below is a dump of /tmp/blender.crash.txt

 
# backtrace
./blender(BLI_system_backtrace+0x1d) [0x11b5d3d]
./blender() [0x8e8d9b]
./blender() [0x8e8f9c]
/lib/x86_64-linux-gnu/libc.so.6(+0x36c30) [0x7fba14556c30]
./blender(BLI_rcti_isect_pt_v+0x4) [0x11a6bb4]
./blender() [0x8fe1c5]
./blender(wm_event_do_handlers+0x2bf) [0x90182f]
./blender(WM_main+0x18) [0x907548]
./blender(main+0x50a) [0x8eb73a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fba14541ec5]
./blender() [0x8e81d7]

**System Information** Linux jdenning-Notebook 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Intel Corp Haswell-ULT Integrated Graphics Controller **Blender Version** Broken: 2.73 273fa0a on Linux and dcc5997 on Mac Worked: 2.73 fdddd4e on Windows 64 **Short description of error** Calling `bpy.ops.screen.screen_full_area()` multiple times in python console causes Blender to crash. Note: calling the first time returns `{'FINISHED'}`, but the second time (switching away from full-area mode) does not return anything. In fact, except for coming out of full-area mode, the console acts as if it didn't execute anything. **Exact steps for others to reproduce the error** - Open the standard/default start-up .blend file (with info, 3D view, outliner, properties, timeline). - Change timeline area to Python console. - Type `bpy.ops.screen.screen_full_area()` and press enter. (console now takes up full window) - Press up arrow then enter to call function again. (Note that the line is still there) - Press enter to call the function again. (no need to press up!) - Repeat last two steps multiple times will cause Blender to crash after 1 to many times, usually within 10 calls. Below is a dump of `/tmp/blender.crash.txt` ```# Blender 2.73 (sub 0), Commit date: 2014-12-23 15:42, Hash 273fa0a # backtrace ./blender(BLI_system_backtrace+0x1d) [0x11b5d3d] ./blender() [0x8e8d9b] ./blender() [0x8e8f9c] /lib/x86_64-linux-gnu/libc.so.6(+0x36c30) [0x7fba14556c30] ./blender(BLI_rcti_isect_pt_v+0x4) [0x11a6bb4] ./blender() [0x8fe1c5] ./blender(wm_event_do_handlers+0x2bf) [0x90182f] ./blender(WM_main+0x18) [0x907548] ./blender(main+0x50a) [0x8eb73a] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fba14541ec5] ./blender() [0x8e81d7] ```

jon denning commented

2015-01-05 22:24:27 +01:00

Changed status to: 'Open'

jon denning commented

2015-01-05 22:24:27 +01:00

Added subscriber: @gfxcoder

Dalai Felinto commented

2015-01-06 02:46:38 +01:00

Added subscriber: @dfelinto

Dalai Felinto commented

2015-01-06 02:46:38 +01:00

Confirmed in OSX, backtrace:


- 0  0x00000001013ea9e6 in BLI_rcti_isect_pt_v (rect=0xc000000000000038, xy=0x117937e4c) at /Users/dfelinto/blender/git/blender/source/blender/blenlib/intern/rct.c:86
- 1  0x000000010012e0d6 in wm_event_inside_i (event=0x117937e38, rect=0xc000000000000038) at /Users/dfelinto/blender/git/blender/source/blender/windowmanager/intern/wm_event_system.c:2074
- 2  0x000000010012d383 in wm_event_do_handlers (C=0x109d0b9e8) at /Users/dfelinto/blender/git/blender/source/blender/windowmanager/intern/wm_event_system.c:2325
- 3  0x0000000100122a0e in WM_main (C=0x109d0b9e8) at /Users/dfelinto/blender/git/blender/source/blender/windowmanager/intern/wm.c:489
#4  0x000000010011e395 in main (argc=1, argv=0x7fff5fbff780) at /Users/dfelinto/blender/git/blender/source/creator/creator.c:1740

Confirmed in OSX, backtrace: ``` - 0 0x00000001013ea9e6 in BLI_rcti_isect_pt_v (rect=0xc000000000000038, xy=0x117937e4c) at /Users/dfelinto/blender/git/blender/source/blender/blenlib/intern/rct.c:86 - 1 0x000000010012e0d6 in wm_event_inside_i (event=0x117937e38, rect=0xc000000000000038) at /Users/dfelinto/blender/git/blender/source/blender/windowmanager/intern/wm_event_system.c:2074 - 2 0x000000010012d383 in wm_event_do_handlers (C=0x109d0b9e8) at /Users/dfelinto/blender/git/blender/source/blender/windowmanager/intern/wm_event_system.c:2325 - 3 0x0000000100122a0e in WM_main (C=0x109d0b9e8) at /Users/dfelinto/blender/git/blender/source/blender/windowmanager/intern/wm.c:489 #4 0x000000010011e395 in main (argc=1, argv=0x7fff5fbff780) at /Users/dfelinto/blender/git/blender/source/creator/creator.c:1740 ```

Dalai Felinto commented

2015-01-06 02:55:09 +01:00

Added subscribers: @JulianEisel, @jensverwiebe

Dalai Felinto commented

2015-01-06 02:55:09 +01:00

@jensverwiebe could you test this in your system? according to @JulianEisel this happens only in 'custom' builds (not in official/buildbot builds). If that's really the case you may have a clue then.