Blender 2.8 crashes on startup #55722

New Issue

Chris Marn · 2018-07-03T15:04:17+02:00

Chris Marn commented

2018-07-03 15:04:17 +02:00

System Information
Windows 7 Ultimate x64, Nvidia Geforce 8600 GT Fatality Edition (1 GB VRAM)

Blender Version
Broken: (blender-2.80.0-git.e856eb7-windows64)
Worked: (optional)

Short description of error
Blender 2.8 crashes on startup. The black terminal window opens, then the following text appears for a few seconds:

Then, a blank window appears:

After a few seconds, the window closes. If I start Blender again, it crashes again. My monitor resolution is 1680x1050. I don't know if the smaller resolution could cause these issues. My GPU supports OpenGL 3.3. I will attach a system information file generated from Blender 2.79
system-info.txt

Exact steps for others to reproduce the error
Blender crashes when it starts. There is no way to provide a .blend file.

**System Information** Windows 7 Ultimate x64, Nvidia Geforce 8600 GT Fatality Edition (1 GB VRAM) **Blender Version** Broken: (blender-2.80.0-git.e856eb7-windows64) Worked: (optional) **Short description of error** Blender 2.8 crashes on startup. The black terminal window opens, then the following text appears for a few seconds: ![error3.png](https://archive.blender.org/developer/F3855376/error3.png) Then, a blank window appears: ![error2.png](https://archive.blender.org/developer/F3855383/error2.png) After a few seconds, the window closes. If I start Blender again, it crashes again. My monitor resolution is 1680x1050. I don't know if the smaller resolution could cause these issues. My GPU supports OpenGL 3.3. I will attach a system information file generated from Blender 2.79 [system-info.txt](https://archive.blender.org/developer/F3855403/system-info.txt) **Exact steps for others to reproduce the error** Blender crashes when it starts. There is no way to provide a .blend file.

Chris Marn commented

2018-07-03 15:04:17 +02:00

Added subscriber: @Darksider

blender-admin commented

2018-07-03 15:04:17 +02:00

#56193 was marked as duplicate of this issue

blender-admin commented

2018-07-03 15:04:17 +02:00

#56061 was marked as duplicate of this issue

Joshua Leung commented

2018-07-03 16:16:42 +02:00

Added subscriber: @JoshuaLeung

Joshua Leung commented

2018-07-03 16:16:42 +02:00

Does Blender run if you start it with --debug-gpu?

Does Blender run if you start it with `--debug-gpu`?

Chris Marn commented

2018-07-03 19:26:57 +02:00

Yes, it starts with this command

Ray molenkamp commented

2018-07-03 19:33:06 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2018-07-03 19:33:06 +02:00

Can you try the last build from the buildbot and see if it's still an issue? there were some changes to the opengl context done.

Joshua Leung commented

2018-07-04 01:39:29 +02:00

If @Darksider is having the same issue that I've been having on my old laptop (and current dev machine), the problem currently looks like:

 	nvoglv64.dll!0000000076c5c300()	Unknown
 	nvoglv64.dll!0000000076c5c1e8()	Unknown
 	nvoglv64.dll!0000000076c5b4cc()	Unknown
>	blender.exe!immEnd() Line 415	C             <----  "glBindBuffer(GL_ARRAY_BUFFER, 0);"

 	blender.exe!region_draw_emboss(const ARegion * ar, const rcti * scirct, int sides) Line 140	C
 	blender.exe!ED_region_do_draw(bContext * C, ARegion * ar) Line 531	C
 	blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 539	C
 	blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 667	C
 	blender.exe!wm_draw_update(bContext * C) Line 825	C
 	blender.exe!WM_main(bContext * C) Line 550	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 525	C

(Note: Tested with 16878072a4, via the greasepencil-object branch)

Pre-Code Quest, Blender used to crash much earlier (i.e. in Ghost, after window creation - see my comments on #51644). As a result, I currently run Blender via an stderr-filtering Rust wrapper, that runs Blender with the --debug-gpu flag, which is the only way to work around the driver problems on my Nvidia GeForce GT 740M.

If @Darksider is having the same issue that I've been having on my old laptop (and current dev machine), the problem currently looks like: ``` nvoglv64.dll!0000000076c5c300() Unknown nvoglv64.dll!0000000076c5c1e8() Unknown nvoglv64.dll!0000000076c5b4cc() Unknown > blender.exe!immEnd() Line 415 C <---- "glBindBuffer(GL_ARRAY_BUFFER, 0);" blender.exe!region_draw_emboss(const ARegion * ar, const rcti * scirct, int sides) Line 140 C blender.exe!ED_region_do_draw(bContext * C, ARegion * ar) Line 531 C blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 539 C blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 667 C blender.exe!wm_draw_update(bContext * C) Line 825 C blender.exe!WM_main(bContext * C) Line 550 C blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 525 C ``` (Note: Tested with 16878072a499d1b328e8f2eb968e5fd4829d996b, via the `greasepencil-object` branch) Pre-Code Quest, Blender used to crash much earlier (i.e. in Ghost, after window creation - see my comments on #51644). As a result, I currently run Blender via an stderr-filtering Rust wrapper, that runs Blender with the `--debug-gpu` flag, which is the only way to work around the driver problems on my Nvidia GeForce GT 740M.

Ray molenkamp commented

2018-07-04 02:23:34 +02:00

given --debug-gpu works, i thought I might be some kind of race condition again, clement did some work with the context today/yesterday, if it's still an issue can you see if GHOST_TSuccess GHOST_ContextWGL::activateDrawingContext() ever returns false?

given `--debug-gpu` works, i thought I might be some kind of race condition again, clement did some work with the context today/yesterday, if it's still an issue can you see if `GHOST_TSuccess GHOST_ContextWGL::activateDrawingContext()` ever returns false?

Joshua Leung commented

2018-07-04 02:39:59 +02:00

Hmm interesting... will test sometime today and let you know. Hopefully we can get to the bottom of this at last.

Ray molenkamp commented

2018-07-04 03:02:39 +02:00

Yeah given i can't repro it, it's probably gonna be a lot of can you try X can you see if Y... sorry about that...

Chris Marn commented

2018-07-04 14:48:04 +02:00

I tried the latest build, and the problem still persists

Joshua Leung commented

2018-07-23 04:59:43 +02:00

Added subscriber: @OluwaseunPeter

Clément Foucault was assigned by Bastien Montagne

2018-07-24 09:25:05 +02:00

Bastien Montagne commented

2018-08-01 16:07:35 +02:00

Added subscribers: @B_Engstler, @mont29

ChristopherAnderssarian commented

2018-08-01 16:17:57 +02:00

Added subscriber: @ChristopherAnderssarian

Bernhard Engstler commented

2018-08-01 17:54:53 +02:00

Coming from #56193 to this one (which seems to be similar). Exactly the same behaviour.
When starting blender with --factory-startup from the Windows 10 commandline (running as admin) I see the following in the command prompt after the crash:

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x000000006BA092D0
Module : C:\WINDOWS\SYSTEM32\nvoglv64.DLL

Starting with -d --debug-gpu it works but extremely slow, while 2.79b works fine.

Full texts of both scenarios attached as txt file, as well as system info.

Blender2.8-d--debug-gpu.txt

system-info.txt

Blender2.8_--factory-startup.txt

To answer the questions from the other thread:

OS and drivers are fully up-to-date, drivers are from NVIDIA, not OS. Though the latest drivers which support my GPU are from 2016.
--factory-startup commandline option does nothing, still crashes.
Tweaking GPU driver settings (performance/quality) does not fix it.

Coming from #56193 to this one (which seems to be similar). Exactly the same behaviour. When starting blender with --factory-startup from the Windows 10 commandline (running as admin) I see the following in the command prompt after the crash: Error : EXCEPTION_ACCESS_VIOLATION Address : 0x000000006BA092D0 Module : C:\WINDOWS\SYSTEM32\nvoglv64.DLL Starting with -d --debug-gpu it works but extremely slow, while 2.79b works fine. Full texts of both scenarios attached as txt file, as well as system info. [Blender2.8-d--debug-gpu.txt](https://archive.blender.org/developer/F4101291/Blender2.8-d--debug-gpu.txt) [system-info.txt](https://archive.blender.org/developer/F4101290/system-info.txt) [Blender2.8_--factory-startup.txt](https://archive.blender.org/developer/F4101289/Blender2.8_--factory-startup.txt) To answer the questions from the other thread: - OS and drivers are fully up-to-date, drivers are from NVIDIA, not OS. Though the latest drivers which support my GPU are from 2016. - --factory-startup commandline option does nothing, still crashes. - Tweaking GPU driver settings (performance/quality) does not fix it.

Clément Foucault commented

2018-08-14 11:55:56 +02:00

Ok so making sense of the error messages:

Win32 Error# (3221692565): <no system message>
Win32 Error# (3221684237): <no system message>

Reading this it seems that the error code are in fact the lower 16 bits of the full DWORD.

3221692565 > 0xC0072095 > 0x2095 > ERROR_INVALID_VERSION_ARB
3221684237 > 0xC007000D > 0x000D > ERROR_INVALID_DATA

But I think those messages maybe ok because we test every higher versions of OpenGL before trying to get the minimum 3.3 context.

It might be nice if someone with a debug build could confirm it's the case.

Can someone (@JoshuaLeung ?) please test this simple patch P766 and tell me if that changes anything?

Ok so making sense of the error messages: `Win32 Error# (3221692565): <no system message>` `Win32 Error# (3221684237): <no system message>` Reading [this ](https://stackoverflow.com/questions/25467260/getlasterror-for-arb-wgl-errors) it seems that the error code are in fact the lower 16 bits of the full DWORD. `3221692565 > 0xC0072095 > 0x2095 > ERROR_INVALID_VERSION_ARB` `3221684237 > 0xC007000D > 0x000D > ERROR_INVALID_DATA` But I think those messages maybe ok because we test every higher versions of OpenGL before trying to get the minimum 3.3 context. It might be nice if someone with a debug **build** could confirm it's the case. Can someone (@JoshuaLeung ?) please test this simple patch [P766](https://archive.blender.org/developer/P766.txt) and tell me if that changes anything?

Joshua Leung commented

2018-08-15 17:00:49 +02:00

@fclem Yep, this solves the crash here. UI draws normally, and Spring files can be loaded.