Blender crashes opening a .blend file with double click or dragging and dropping it on to the executable #44217

New Issue

Riccardo Giovanetti · 2015-04-01T14:45:34+02:00

2015-04-01 14:45:34 +02:00

System Information
Mobile Intel Core i7 720QM (1.66GHz), Win7 Pro 64bit, 8GB RAM, NVIDIA GTS 360M with 1GB VRAM

Blender Version
Broken: Blender 2.74 64bit (Hash: 000dfc0), (blender-2.74-windows64.zip);
Worked: (optional)

Short description of error
If the option User Preferences | File | Load UI is unchecked, double clicking or dragging and dropping a .blend file over the executable blender.exe causes Blender to start up and close immediately.

Exact steps for others to reproduce the error
What happens is that with the current version 2.74's blender.exe set as the default application to open .blend files when you double click on a .blend file or even dragging and dropping it over the blender.exe program, Blender starts up but then closes immediately generating the following blender.crash.txt log file:

backtrace

18: PyInit_mathutils_noise_types - 0x3FE89230
17: fftw_plan_many_dft - 0x3F2147B0
16: fftw_plan_many_dft - 0x3F2147B0
15: fftw_plan_many_dft - 0x3F2147B0
14: UnhandledExceptionFilter - 0x76F2B7E0
13: MD5Final - 0x770415B0
12: _C_specific_handler - 0x76FC852C
11: RtlDecodePointer - 0x76FD9C80
10: RtlUnwindEx - 0x76FC8610
9: KiUserExceptionDispatcher - 0x7700121A
8: fftw_plan_many_dft - 0x3F2147B0
7: fftw_plan_many_dft - 0x3F2147B0
6: fftw_plan_many_dft - 0x3F2147B0
5: fftw_plan_many_dft - 0x3F2147B0
4: PyInit_mathutils_noise_types - 0x3FE89230
3: fftw_plan_many_dft - 0x3F2147B0
2: osl_trunc_vv - 0x416A3110
1: BaseThreadInitThunk - 0x76EA59E0
0: RtlUserThreadStart - 0x76FDC520

So I restored all the default settings and checking all my changes to the preferences one by one I found that what apparently seems to cause this behaviour is the "Load UI" option if unchecked. If you reinstate it (checked) opening automatically the file .blend as well as dragging and dropping the .blend file over the executable (blender.exe) works fine. I cannot be sure anyway that other setting might produce the same problem, at least this is what I found out.

**System Information** Mobile Intel Core i7 720QM (1.66GHz), Win7 Pro 64bit, 8GB RAM, NVIDIA GTS 360M with 1GB VRAM **Blender Version** Broken: Blender 2.74 64bit (Hash: 000dfc0), (blender-2.74-windows64.zip); Worked: (optional) **Short description of error** If the option User Preferences | File | Load UI is unchecked, double clicking or dragging and dropping a .blend file over the executable blender.exe causes Blender to start up and close immediately. **Exact steps for others to reproduce the error** What happens is that with the current version 2.74's blender.exe set as the default application to open .blend files when you double click on a .blend file or even dragging and dropping it over the blender.exe program, Blender starts up but then closes immediately generating the following blender.crash.txt log file: # backtrace 18: PyInit_mathutils_noise_types - 0x3FE89230 17: fftw_plan_many_dft - 0x3F2147B0 16: fftw_plan_many_dft - 0x3F2147B0 15: fftw_plan_many_dft - 0x3F2147B0 14: UnhandledExceptionFilter - 0x76F2B7E0 13: MD5Final - 0x770415B0 12: _C_specific_handler - 0x76FC852C 11: RtlDecodePointer - 0x76FD9C80 10: RtlUnwindEx - 0x76FC8610 9: KiUserExceptionDispatcher - 0x7700121A 8: fftw_plan_many_dft - 0x3F2147B0 7: fftw_plan_many_dft - 0x3F2147B0 6: fftw_plan_many_dft - 0x3F2147B0 5: fftw_plan_many_dft - 0x3F2147B0 4: PyInit_mathutils_noise_types - 0x3FE89230 3: fftw_plan_many_dft - 0x3F2147B0 2: osl_trunc_vv - 0x416A3110 1: BaseThreadInitThunk - 0x76EA59E0 0: RtlUserThreadStart - 0x76FDC520 So I restored all the default settings and checking all my changes to the preferences one by one I found that what apparently seems to cause this behaviour is the "Load UI" option if unchecked. If you reinstate it (checked) opening automatically the file .blend as well as dragging and dropping the .blend file over the executable (blender.exe) works fine. I cannot be sure anyway that other setting might produce the same problem, at least this is what I found out.

Riccardo Giovanetti commented

2015-04-01 14:45:34 +02:00

Changed status to: 'Open'

Riccardo Giovanetti commented

2015-04-01 14:45:34 +02:00

Added subscriber: @Harvester

blender-admin commented

2015-04-01 14:45:34 +02:00

#44063 was marked as duplicate of this issue

Ray molenkamp commented

2015-04-01 16:59:04 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2015-04-01 16:59:04 +02:00

null de-ref here

https://git.blender.org/gitweb/gitweb.cgi/blender.git/blob/HEAD:/source/blender/blenkernel/intern/blender.c#l286

	if (curscreen)
		curscene = curscreen->scene;

seems to fix it.

null de-ref here https://git.blender.org/gitweb/gitweb.cgi/blender.git/blob/HEAD:/source/blender/blenkernel/intern/blender.c#l286 if (curscreen) curscene = curscreen->scene; seems to fix it.

Antonis Ryakiotakis commented

2015-04-01 17:34:28 +02:00

Added subscriber: @Psy-Fi

Antonis Ryakiotakis commented

2015-04-01 17:34:28 +02:00

Confirmed, this is a bit serious, setting to high priority

Ray Mairlot commented

2015-04-01 20:22:19 +02:00

Added subscribers: @sicutunum, @mont29

sicutunum commented

2015-04-01 20:45:27 +02:00

This comment was removed by @sicutunum

*This comment was removed by @sicutunum*

Aaron Carlisle commented

2015-04-01 20:53:48 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-04-01 20:53:48 +02:00

hey hey the bug is still going to be resolved no matter who posted it

sicutunum commented

2015-04-01 20:55:32 +02:00

Yes I know. It's awesome when no one respects your voice enough to test a bug that will disable thousands of users upon release:

https://developer.blender.org/T44063

Yes I know. It's awesome when no one respects your voice enough to test a bug that will disable thousands of users upon release: https://developer.blender.org/T44063

sicutunum commented

2015-04-01 21:04:36 +02:00

Sorry to come off as such a whiner. This place is about getting things done not drama. Nobody sucks. I'm sorry. I need to check my blood sugar.