Page MenuHome

Unchecking Load UI setting crashes Blender when opening a file
Closed, DuplicatePublic


System Information
Windows 7
NVIDIA GeForce GT740
AMD FX-6120
16 GB DDR3

Blender Version
Broken: 2.74 Release Candidate (Windows 64 Installer)
Worked: 2.73a

Short description of error
After turning off the setting "Load UI" in the user preferences, Blender will crash any saved file you click to open. I'm only certain this error occurs on my machine and with the Windows 64 bit Installer version of 2.74 RC. Sorry if this is not the area to report release candidate bugs, please correct me if it's not so I can post in the proper area next time.

Exact steps for others to reproduce the error
Open Blender
Go to File/User Preferences/ Select the File Tab
Uncheck "Load UI" setting and press "Save User Settings".
Save your current Blend file anywhere on your hardrive (any blend file and name it anything)
Close Blender
Click on the Blend file you saved to open it up
Blender crashes (note: this does not happen when loading the file from Blender's file manager)



Event Timeline

sicutunum updated the task description. (Show Details)Mar 20 2015, 3:50 PM
sicutunum added a project: BF Blender.
sicutunum set Type to Bug.
sicutunum added a subscriber: sicutunum.
sicutunum created this task.
sicutunum raised the priority of this task from to Needs Triage by Developer.

Sorry, forgot to mention the date and hash of this build:

2015-03-11 15:49
Hash: 4aa5109

Bastien Montagne (mont29) triaged this task as Needs Information from User priority.

I cannot confirm that here (current master, linux64). Please:

  • Ensure both your OS and drivers are fully up-to-date.
  • For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine.
  • Try the latest build from our buildbot.
  • Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
  • Try to tweak OGL settings in UserPreferences, System tab.
  • Attach here the report generated by Help -> System Info.
  • Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).

I tried downloading one of those builds, couldn't find the .exe installer which is what this issue pertains to. Instead, downloaded the latest windows64 .exe release from


The version is:
2015-03-17 15:11
Hash: 1f547c1

Same problem still persists. Completely uninstalled Blender and all additional settings, folders and files, reinstalled and still crashes when attempt to open a .blend file from outside of Blender. (Blender opens fine when opening from the shortcut to the .exe or opening a .blend file from the Blender file manager). Whenever userpref.blend and startup.blend are removed from the config folder that is generated in roaming/blenderfoundation/blender/2.74 then it will open again. Whatever's causing it to crash is something generated in those files when either the user preferences or startup file is saved (it seems it will crash with either one remaining in the config folder).

• OS is fine
• I do a lot of Blender things, everything is up to date and cool on my computer
• This test was done on a fresh install of Blender, factory settings no changes, then immediately tested.

Here is the system info readout. This needs to be tested on a Windows 7 machine using the installer with the steps I described followed.

Bastien Montagne (mont29) raised the priority of this task from Needs Information from User to Normal.

Just tested this issue on a Windows Vista machine that has never had Blender installed on it before with the latest March 26 blender-2.74-rc4-windows64.exe
The problem is still there, I'm guessing this issue is occurring for every Windows machine. So anyone one using Windows who doesn't like their user preferences to be smashed when opening a Blend file, will not be able to open any Blender file at all without it immediately crashing Blender. I don't understand why this isn't getting more attention, or why no one's even bothered to confirm this.