blender randomly crashes when sharing session with other 3D programs #98723

New Issue

Alberto Velázquez · 2022-06-09T12:33:30+02:00

2022-06-09 12:33:30 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e3691
Worked: 2.8

Short description of error
I apologize in advance because I've been seeing this problem since blender 3.0 (maybe 2.93 but I don't remember now) but I've never been able to report it because of its rarity, randomness and I find myself unable to create a normal, standardized bug report.

Sometimes (as far as I know only on Windows, in my case 10), and not always, blender cannot create new windows if another (usually 3D) program is also open. Sometimes it happens to me with 3DsMax2020, sometimes with Affinity Photo, sometimes with Painter, and almost always with unreal in the background and 3DsMax2020, without any other such program loaded.

What do I mean by not being able to generate new windows? I can keep the blender session I have open at that moment, but I can not...

Create new blender sessions (or new instances of the program, as you prefer to understand it).
I can't create new windows inside the blender session I already have open (for example to save the file or to export it). So I have to save without opening any window (the usual when using ctrl+s) or I have to export using a plugin I have that uses a preset and doesn't need to open the export window. And if I try it then blender crashes.

It is not that blender makes a crash when I try to open it, it simply doesn't open, you can see how it tries to create a window, but you can only see the borders of it and it disappears in tenths of a second. No log is generated that I can use for the report. Reason why I have never reported, but seeing that it persists after 3.0, 3.1 and 3.2, I am forced to report.

The only way to solve this bug that I have found is to close the windows session and open it again (no need to reboot).

Do I do something in particular that triggers the bug? No, it can happen to me as soon as I open blender without doing anything just by opening 3DsMAX, there is no process to reproduce the bug.

When this happens do I start having similar problems with other programs? Yes, when this happens sometimes I can't open 3DsMAX 2020 and neither Painter or Affinity (but not always).

Did it start to happen to me because of blender? It started to happen to me when I updated blender, because I have not updated 3DsMAX nor changed the operating system.

I'm sorry I can't give more and more precise information.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: `e05e1e3691` Worked: 2.8 **Short description of error** I apologize in advance because I've been seeing this problem since blender 3.0 (maybe 2.93 but I don't remember now) but I've never been able to report it because of its rarity, randomness and I find myself unable to create a normal, standardized bug report. Sometimes (as far as I know only on Windows, in my case 10), and not always, blender cannot create new windows if another (usually 3D) program is also open. Sometimes it happens to me with 3DsMax2020, sometimes with Affinity Photo, sometimes with Painter, and almost always with unreal in the background and 3DsMax2020, without any other such program loaded. What do I mean by not being able to generate new windows? I can keep the blender session I have open at that moment, but I can not... - Create new blender sessions (or new instances of the program, as you prefer to understand it). - I can't create new windows inside the blender session I already have open (for example to save the file or to export it). So I have to save without opening any window (the usual when using ctrl+s) or I have to export using a plugin I have that uses a preset and doesn't need to open the export window. And if I try it then blender crashes. It is not that blender makes a crash when I try to open it, it simply doesn't open, you can see how it tries to create a window, but you can only see the borders of it and it disappears in tenths of a second. No log is generated that I can use for the report. Reason why I have never reported, but seeing that it persists after 3.0, 3.1 and 3.2, I am forced to report. The only way to solve this bug that I have found is to close the windows session and open it again (no need to reboot). Do I do something in particular that triggers the bug? No, it can happen to me as soon as I open blender without doing anything just by opening 3DsMAX, there is no process to reproduce the bug. When this happens do I start having similar problems with other programs? Yes, when this happens sometimes I can't open 3DsMAX 2020 and neither Painter or Affinity (but not always). Did it start to happen to me because of blender? It started to happen to me when I updated blender, because I have not updated 3DsMAX nor changed the operating system. I'm sorry I can't give more and more precise information.

Alberto Velázquez commented

2022-06-09 12:33:30 +02:00

Added subscriber: @AlbertoVelazquez

Thomas Dinges commented

2022-06-09 13:17:17 +02:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2022-06-09 13:17:17 +02:00

I cannot confirm this here. I opened Blender 3.2, also opened the Affinity Suite (Photo, Designer and Publisher). I can open another Blender instance without issues or create a new window from within the first open Blender instance. Windows 10 here as well.

Alberto Velázquez commented

2022-06-09 13:18:48 +02:00

Just to be clear, it is very difficult to reproduce, it can happen to me 3 times in a row and then not happen to me for 2 weeks.

Richard Antalik commented

2022-06-09 18:14:55 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-06-09 18:14:55 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2022-06-09 18:14:55 +02:00

@AlbertoVelazquez Please download alpha build from https://builder.blender.org/download/daily/ and run file blender_debug_log.cmd. When problem happens, close Blender and upload created files. Hopefully there will be some error message present, I would expect crash if window fails to initialize.

@AlbertoVelazquez Please download alpha build from https://builder.blender.org/download/daily/ and run file `blender_debug_log.cmd`. When problem happens, close Blender and upload created files. Hopefully there will be some error message present, I would expect crash if window fails to initialize.

Alberto Velázquez commented

2022-06-09 20:34:54 +02:00

Ok, I will do, but probably I will need some time to show a log.

Alberto Velázquez commented

2022-06-23 11:51:07 +02:00

In #98723#1371749, @iss wrote:
@AlbertoVelazquez Please download alpha build from https://builder.blender.org/download/daily/ and run file blender_debug_log.cmd. When problem happens, close Blender and upload created files. Hopefully there will be some error message present, I would expect crash if window fails to initialize.

Like previus versions the blender debug is empty

blender_debug_output.txt

> In #98723#1371749, @iss wrote: > @AlbertoVelazquez Please download alpha build from https://builder.blender.org/download/daily/ and run file `blender_debug_log.cmd`. When problem happens, close Blender and upload created files. Hopefully there will be some error message present, I would expect crash if window fails to initialize. Like previus versions the blender debug is empty [blender_debug_output.txt](https://archive.blender.org/developer/F13220338/blender_debug_output.txt)

Alberto Velázquez commented

2022-06-23 11:52:04 +02:00

One thing is that the bug is shared between all blender versions... so If I have the problem with blender 3.1 o 3.2 I cannot open 3.3 also.

Richard Antalik commented

2022-06-23 18:56:32 +02:00

Unfortunately I have no idea why this would happen.

One thing you can check is opengl emulation:
Download mesa3d-21.3.5-release-msvc.7z from github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe.
This will enable opengl emulation, which will be slow, but if it will work correctly, this means that issue is within GPU driver or possibly other system library.

Another thing could be to check if you can work normally, when you set Preferences > Interface > Temporary Editors > File Browser to Maximized Area. You may set Render In option as well to maximized area.

Which also brings another question - does this also happen when you render image? Will window fail to initialize?

Unfortunately I have no idea why this would happen. One thing you can check is opengl emulation: Download mesa3d-21.3.5-release-msvc.7z from github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe. This will enable opengl emulation, which will be slow, but if it will work correctly, this means that issue is within GPU driver or possibly other system library. Another thing could be to check if you can work normally, when you set Preferences > Interface > Temporary Editors > File Browser to Maximized Area. You may set Render In option as well to maximized area. Which also brings another question - does this also happen when you render image? Will window fail to initialize?

Alberto Velázquez commented

2022-06-23 21:45:13 +02:00

Ok, I will do the next time that this happens.

I don't make renders since a lot of time ago, so I didn't test it.

Ok, I will do the next time that this happens. I don't make renders since a lot of time ago, so I didn't test it.

Pratik Borhade commented

2022-08-18 07:43:08 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-08-18 07:43:08 +02:00

@AlbertoVelazquez hi, any news? have you managed to repro it again?

When this happens do I start having similar problems with other programs? Yes, when this happens sometimes I can't open 3DsMAX 2020 and neither Painter or Affinity (but not always).

You mean when blender instance is running, you can't open other software?

@AlbertoVelazquez hi, any news? have you managed to repro it again? > When this happens do I start having similar problems with other programs? Yes, when this happens sometimes I can't open 3DsMAX 2020 and neither Painter or Affinity (but not always). You mean when blender instance is running, you can't open other software?

Alberto Velázquez commented

2022-08-18 14:28:18 +02:00

I'm in holidays since July, so I cannot test it again.

To your last question, yes, I cannot open some types of software (the internet browser can be opened)

I'm in holidays since July, so I cannot test it again. To your last question, yes, I cannot open some types of software (the internet browser can be opened)

Alberto Velázquez commented

2022-09-08 20:47:07 +02:00

In #98723#1379144, @iss wrote:
Unfortunately I have no idea why this would happen.

One thing you can check is opengl emulation:
Download mesa3d-21.3.5-release-msvc.7z from github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe.
This will enable opengl emulation, which will be slow, but if it will work correctly, this means that issue is within GPU driver or possibly other system library.

Another thing could be to check if you can work normally, when you set Preferences > Interface > Temporary Editors > File Browser to Maximized Area. You may set Render In option as well to maximized area.

Which also brings another question - does this also happen when you render image? Will window fail to initialize?

Hi Richard, finally I go back to work and I can find the problem again (this time in windows 11 with blender 3.2) and I tried to put the DLLs in the folder but bug still happens

> In #98723#1379144, @iss wrote: > Unfortunately I have no idea why this would happen. > > One thing you can check is opengl emulation: > Download mesa3d-21.3.5-release-msvc.7z from github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe. > This will enable opengl emulation, which will be slow, but if it will work correctly, this means that issue is within GPU driver or possibly other system library. > > Another thing could be to check if you can work normally, when you set Preferences > Interface > Temporary Editors > File Browser to Maximized Area. You may set Render In option as well to maximized area. > > Which also brings another question - does this also happen when you render image? Will window fail to initialize? Hi Richard, finally I go back to work and I can find the problem again (this time in windows 11 with blender 3.2) and I tried to put the DLLs in the folder but bug still happens

Richard Antalik commented

2022-09-13 22:00:43 +02:00

Thanks for information. By "this time in windows 11" do you mean that you reinstalled OS and this issue still happens? In such case I am truly out of ideas. HW failure would likely result in whole OS going down, so I don't think that is the cause either.

Perhaps do you use some software that alters Windows behavior, like virtual desktops or special window modifications?

Thanks for information. By "this time in windows 11" do you mean that you reinstalled OS and this issue still happens? In such case I am truly out of ideas. HW failure would likely result in whole OS going down, so I don't think that is the cause either. Perhaps do you use some software that alters Windows behavior, like virtual desktops or special window modifications?

Alberto Velázquez commented

2022-09-14 09:25:00 +02:00

No, I updated windows 10, not a clean installation.

I don't have windows modifications and I'm really convinced that the problem is something with the graphic system. Because the other day I needed to made renders of my assets for a game (with cycles) and open constantly some assets to render give me the problem each 10 minutes. Like never before.

What I need to ask, what can crash blender, and other programs, before of have the log?

No, I updated windows 10, not a clean installation. I don't have windows modifications and I'm really convinced that the problem is something with the graphic system. Because the other day I needed to made renders of my assets for a game (with cycles) and open constantly some assets to render give me the problem each 10 minutes. Like never before. What I need to ask, what can crash blender, and other programs, before of have the log?

Richard Antalik commented

2022-09-15 03:15:46 +02:00

I see. Personally I would recommend to do clean install. There were number of reports where this resolved issues with random crashes on hardware that other users never had similar issues, and I have never seen report like this (I saw a lot of reports).

Richard Antalik commented

2022-11-11 19:21:47 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Richard Antalik closed this issue

2022-11-11 19:21:47 +01:00

Richard Antalik commented

2022-11-11 19:21:47 +01:00

There has been no update for quite some time and nature of the issue is unlikely to be a bug in Bender, so I will close this report. Hopefully it's resolved...

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

blender randomly crashes when sharing session with other 3D programs #98723