Maniphest T43183

Blender closes instantly
Closed, Archived

Assigned To
Julian Eisel (Severin)
Authored By
Wo!262 (wo262)
Jan 9 2015, 4:04 PM
Tags
  • BF Blender
  • Platform: Windows
Subscribers
Bastien Montagne (mont29)
Julian Eisel (Severin)
Wo!262 (wo262)

Description

System Information
Windows 8.1 x64
Intel Pentium E2180 @ 2.00GHz
Intel 82945G Express Chipset Family OpenGL 1.1
2gb ram

Blender Version
Broken: 2.73 x64 official release. Can't see splashcreen
Worked: 2.72b x64 official release.

Short description of error
Blender crashes immediately after opening it. I can see the Blender window for a fraction of a second and then it closes. Nothing happens after that, there is no error or crash window or anything. It just closes.

Exact steps for others to reproduce the error
Just open it with a similar rig. However, I reported a similar error before, T39706, but it was disregarded as a fault of the unsupported Intel gpu. It turned out that I had problems with my user files, that was my fault and I fixed it deleting my user files. Nothing to do with the gpu. I thought now it could be the same, but after using other user files, and manually disabling addons, it still won't open. This is all I did:

Installing a clean copy of 2.73 x64. At this point there is no user folder at /users/admin/appdata/roaming/blender foundation/blender - Blender instantly closes

Downloading zipped versions of 2.73, both 32 and 64 bit - Both Blender(s) instantly close.

Manually copying user files from 2.72 folder to a new 2.73 folder - Blender instantly closes, but I could see the previous theme and layout configuration I had during that instant.

Disabling folders one at a time at /program files/blender foundation/blender/2.73/scripts to do some amateur debugging - Blender instantly closes, sometimes I can see some things dissapearing but that's it, it closes nonetheless.

Reinstalling the older 2.72b - It works perfectly.

Installing 2.73, 32 bit on another computer. Windows8 32 bit, 1gb of ram, Intel Atom N450, Intel GMA 3150 OpenGL 1.4 - It works perfectly

Hopefully it isn't GPU related
Since 2.72 works perfectly I don't think it is the GPU though I know you will drop support for OpenGL 1.1 in the future. In the meantime I will report it as bug. Thanks for your hard work.

Event Timeline

Wo!262 (wo262) created this task.Jan 9 2015, 4:04 PM
Wo!262 (wo262) raised the priority of this task from to 90.
Wo!262 (wo262) updated the task description.
Wo!262 (wo262) added a project: BF Blender.
Wo!262 (wo262) edited a custom field.
Wo!262 (wo262) added a subscriber: Wo!262 (wo262).
Bastien Montagne (mont29) lowered the priority of this task from 90 to 30.Jan 9 2015, 4:12 PM
Bastien Montagne (mont29) added a subscriber: Bastien Montagne (mont29).

It is most likely GPU related - if one dare to call 945 a GPU… seriously.

Anyway, please:

  • Ensure both your OS and drivers are fully up-to-date;
  • Try to start Blender in factory settings (--factory-startup commandline option).
  • Try to tweak OGL settings in UserPreferences, System tab.
  • 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).
Bastien Montagne (mont29) added a comment.Jan 9 2015, 4:17 PM

Also, Intel945 is supposed to be OpenGL1.4, if your OS (or Blender) reports only OpenGL1.1, you probably do not have GPU drivers installed at all (i.e. you fall back on windows software OGL, with which Blender does not work).

Bastien Montagne (mont29) added a project: Platform: Windows.Jan 9 2015, 4:18 PM
Wo!262 (wo262) added a comment.Jan 9 2015, 5:15 PM

Placing the DLL does work. Also, my driver was up to date, and for whatever reason, downgrading it to a previous version fixed the problem and it's now ogl1.4. Thanks.

Will you keep this bug as open? The fact that 2.72 works with ogl1.1 and 2.73 doesn't, makes it more of a general bug and not just my personal problem. But if the bug only happens with Intel and not with older nVidia or Ati that only support ogl1.1 then it falls out from the official dev support.

Julian Eisel (Severin) changed the task status from Unknown Status to Resolved.Jan 9 2015, 5:20 PM
Julian Eisel (Severin) claimed this task.

IIRC, we had similar reports which were fixed by downgrading the graphics drivers, so this seems to be a driver bug in the newest version.

Anyway, glad it's working again. Looks like this can be closed :)

Julian Eisel (Severin) changed the task status from Resolved to Archived.Jan 9 2015, 5:25 PM

Ehh, better set it to "Invalid", as it was caused from external drivers.