Project closes automatically when double-clicking the file to open it #120352

New Issue

Sebastien Larocque · 2024-04-07T04:33:08+02:00

2024-04-07 04:33:08 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86

Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270
Worked: 4.0

Short description of error
Project closes automatically when double-clicking the file to open it

Exact steps for others to reproduce the error

Download the attached file “ProjectClosesAutomatically.blend”.
Double-click the file to open it.
At that point, the file opens and closes (or crashes) in a very short time.

Note that I work on Windows 10.

Context

This project file is a large and complex project that I’ve been working for a long time. I worked on different versions of Blender with it. Just before version 4.1 was released, I had been testing with the daily builds and in the beta and RC versions. At that point, I opened Blender manually from the unzipped folder from the zip file. Then I dragged and dropped my project file in Blender. That worked. When version 4.1 was officially released, I installed it and I started again to double-click the project file to open it. From this moment, Blender started crashing. My other projects work normally, it is just this project.

Workaround

To isolate the problem, I decided to make a copy and to remove progressively all the stuff. It had been crashing even when everything was removed.

I decided to open the project file from the “File | Open” menu and to uncheck the “Load UI”. Saving the file and closing Blender to reopen it after by double-clicking the project file in the folder made it work again normally. I suspect that it is something related to the UI.

The project also has two windows. It has a second main window. If I close the second window, save the project, close it and then double-click to open the file again, it does not crash. Probably the UI and related to the second window open.

Note that the project file is about 8.6 MB with nothing in it even after stripping the content. It looks like a new project and I also removed the orphans. It is still far bigger than a brand new project. Something must still be in the project but not shown. The size is too big for the project content.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86 **Blender Version** Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270` Worked: 4.0 **Short description of error** Project closes automatically when double-clicking the file to open it **Exact steps for others to reproduce the error** * Download the attached file “ProjectClosesAutomatically.blend”. * Double-click the file to open it. * At that point, the file opens and closes (or crashes) in a very short time. Note that I work on Windows 10. **Context** This project file is a large and complex project that I’ve been working for a long time. I worked on different versions of Blender with it. Just before version 4.1 was released, I had been testing with the daily builds and in the beta and RC versions. At that point, I opened Blender manually from the unzipped folder from the zip file. Then I dragged and dropped my project file in Blender. That worked. When version 4.1 was officially released, I installed it and I started again to double-click the project file to open it. From this moment, Blender started crashing. My other projects work normally, it is just this project. **Workaround** To isolate the problem, I decided to make a copy and to remove progressively all the stuff. It had been crashing even when everything was removed. I decided to open the project file from the “File | Open” menu and to uncheck the “Load UI”. Saving the file and closing Blender to reopen it after by double-clicking the project file in the folder made it work again normally. I suspect that it is something related to the UI. The project also has two windows. It has a second main window. If I close the second window, save the project, close it and then double-click to open the file again, it does not crash. Probably the UI and related to the second window open. Note that the project file is about 8.6 MB with nothing in it even after stripping the content. It looks like a new project and I also removed the orphans. It is still far bigger than a brand new project. Something must still be in the project but not shown. The size is too big for the project content.

ProjectClosesAutomatically2.blend

7.9 MiB

Sebastien Larocque added the

labels 2024-04-07 04:33:09 +02:00

Pratik Borhade commented

2024-04-07 07:53:17 +02:00

Hi, thanks for the report. Unable to confirm the crash in 4.1. Given that crash is observed when double clicked on file, I'd be interested to know whether registered blender version to open files is 4.1?
I would suggest to first register 4.1 as default to open files: Edit > Preferences > System > Register -> Save Preferences
Now open file by double clicking from windows explorer. Let us know if it still crashes

Hi, thanks for the report. Unable to confirm the crash in 4.1. Given that crash is observed when double clicked on file, I'd be interested to know whether registered blender version to open files is 4.1? I would suggest to first register 4.1 as default to open files: `Edit > Preferences > System > Register` -> Save Preferences Now open file by double clicking from windows explorer. Let us know if it still crashes

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-04-07 07:53:49 +02:00

Sebastien Larocque commented

2024-04-07 20:14:42 +02:00

I understand that opening the file by double-clicking on it does not crash or close the project for you. That’s strange.

I did what you asked to register Blender and it did not change anything. It did it twice. I also tested several times to double-click with my original project and the test project stripped from my original project.

Even when it closed automatically, I could quickly see that version number in the bottom-right corner and that was 4.1.0. I guess that it opened the right version of Blender.

I did other tests to open older projects that I got by double-clicking. They open correctly when there is only one main window and also another rendered window. Those that have the main window and another main window crash about one second after they are open. I work with two monitors where I usually have the main window on my main monitor and a second window on my second monitor where the layout tab is selected and shows the Cycles preview. Sometimes, I have the rendered window too. It is those projects that crash when double-clicking.

I’ve just uninstalled all versions of Blender (3.6, 4.0, 4.1) and reinstalled 4.1.

I tested again the test project. I discovered that I left some stuff in the world shader. I deleted it and uploaded the project again under the name “ProjectClosesAutomatically2.blend”. The problem is still there.

I've just made a strange test from “ProjectClosesAutomatically2.blend”. It seems to explain the real nature of the problem. You can reproduce it:

The test file is 8,140 KB (with virtually nothing inside, it’s the same thing as a new project, but about 8 times larger).
Open Blender 4.1.
Drag and drop the test file in Blender.
Close the second main window, save the project and quit Blender”
The test file is now 6,182 KB. What in the world can reduce the file size of about 25%?
Double-click the test file. Blender opens correctly without crashing.
Create a new main window and save.
The test file is now 4,964 KB. I don’t understand!

This is where I just discovered something here. It does not crash after this last test, but I made it crash again. Here’s the factor that created the difference. In the second main window, the view is split in the layout tab. If I double-click the test file when the second window is split, it does not crash. If I double-click the test file with the maximized right part of the split view, Blender crashes.

I joined the new test file here at the stage where the right part of the split view is maximized. It should crash if you double-click it.

I tested again more extensively. I tested with one main window and the view maximized. It does not crash. I tested with two main windows, but this time with the maximized view in the first main window and it does not crash. I tried again with only the view maximized in the second main window and it crashed like expected.

To reproduce the problem from the start, I created a brand new project where I created a second main window and I maximized the view as described above. I closed the project to double-click the file and it crashed in the same way. If the view is not maximized, it does not crash. The file size if 1,143 KB, which is the normal size for a project with almost nothing in it. Yet, the other test file is several times this size with the same content. Very strange. I also joined the new test “BlandNewProjectMaximizedView.blend”

Bottom line, I want to draw your attention to the precise case of the maximized view in the second main window and also that the file size is abnormally big for a project is supposed to be empty like a brand new project.

I hope this allows to investigate further.

I understand that opening the file by double-clicking on it does not crash or close the project for you. That’s strange. I did what you asked to register Blender and it did not change anything. It did it twice. I also tested several times to double-click with my original project and the test project stripped from my original project. Even when it closed automatically, I could quickly see that version number in the bottom-right corner and that was 4.1.0. I guess that it opened the right version of Blender. I did other tests to open older projects that I got by double-clicking. They open correctly when there is only one main window and also another rendered window. Those that have the main window and another main window crash about one second after they are open. I work with two monitors where I usually have the main window on my main monitor and a second window on my second monitor where the layout tab is selected and shows the Cycles preview. Sometimes, I have the rendered window too. It is those projects that crash when double-clicking. I’ve just uninstalled all versions of Blender (3.6, 4.0, 4.1) and reinstalled 4.1. I tested again the test project. I discovered that I left some stuff in the world shader. I deleted it and uploaded the project again under the name “ProjectClosesAutomatically2.blend”. The problem is still there. I've just made a strange test from “ProjectClosesAutomatically2.blend”. It seems to explain the real nature of the problem. You can reproduce it: - The test file is 8,140 KB (with virtually nothing inside, it’s the same thing as a new project, but about 8 times larger). - Open Blender 4.1. - Drag and drop the test file in Blender. - Close the second main window, save the project and quit Blender” - The test file is now 6,182 KB. What in the world can reduce the file size of about 25%? - Double-click the test file. Blender opens correctly without crashing. - Create a new main window and save. - The test file is now 4,964 KB. I don’t understand! This is where I just discovered something here. It does not crash after this last test, but I made it crash again. Here’s the factor that created the difference. In the second main window, the view is split in the layout tab. If I double-click the test file when the second window is split, it does not crash. If I double-click the test file with the maximized right part of the split view, Blender crashes. I joined the new test file here at the stage where the right part of the split view is maximized. It should crash if you double-click it. I tested again more extensively. I tested with one main window and the view maximized. It does not crash. I tested with two main windows, but this time with the maximized view in the first main window and it does not crash. I tried again with only the view maximized in the second main window and it crashed like expected. To reproduce the problem from the start, I created a brand new project where I created a second main window and I maximized the view as described above. I closed the project to double-click the file and it crashed in the same way. If the view is not maximized, it does not crash. The file size if 1,143 KB, which is the normal size for a project with almost nothing in it. Yet, the other test file is several times this size with the same content. Very strange. I also joined the new test “BlandNewProjectMaximizedView.blend” Bottom line, I want to draw your attention to the precise case of the maximized view in the second main window and also that the file size is abnormally big for a project is supposed to be empty like a brand new project. I hope this allows to investigate further.

BlandNewProjectMaximizedView.blend

1.1 MiB

ProjectClosesAutomatically3.blend

4.8 MiB

YimingWu commented

2024-04-08 04:42:27 +02:00

Can't seem to reproduce the issue with two screens and maximized view. Could be a windows specific problem.

@SebBlender Are you sure you have factory-reset blender and try this? It could be a plugin error since the windows open fine for like a brief moment.

Could you try and see if there's any crash log? Thanks!

Can't seem to reproduce the issue with two screens and maximized view. Could be a windows specific problem. @SebBlender Are you sure you have factory-reset blender and try this? It could be a plugin error since the windows open fine for like a brief moment. Could you try and see if there's any [crash log](https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#windows)? Thanks!

Sebastien Larocque commented

2024-04-09 17:04:46 +02:00

I have more information

I joined the crash log here. Let me know if you can do something with this.

Concerning the factory setting and the plugins (or add-ons) issues, I started disabling the add-ons that have one by one. I quickly found that “BlenderKit Online Asset Library” is probably the problem. If I disable it without uninstalling it and I double-click the problematic blender file, it does not crash.

BlenderKit version is 3.11.0.240207. It seems the latest version according to their update checker.

If the add-on is not enabled and I go the preferences window to enable it, the moment that I click the checkbox Blender crashes. That is, of course, only for the Blender file with the problematic window configuration.

Now, three questions remain to me.

Should I report this bug to the BlenderKit creator.
Does Blender have some responsibility by letting this add-on crash the whole software at start-up?
Why is this problem present only when double-clicking the blend file and not when loading the file through the menu or drag-and-drop? I feel that order that things are loaded when double-clicking the blend file is different from opening Blender and then loading the blend file. Probably that Blender has more time to complete loading a certain module for example and when loading the blender file after, everything is ready to be used. It is such a precise scenario under very specific conditions to crash Blender that it makes me think that the execution is quite convoluted.

Edit: I just made another test quickly and I discovered that opening Blender from the start menu (no project), creating a second main window (nothing more and not maximized view in that case) and going to the preferences window and enabling BlenderKit also makes it crash.

I have more information I joined the crash log here. Let me know if you can do something with this. Concerning the factory setting and the plugins (or add-ons) issues, I started disabling the add-ons that have one by one. I quickly found that “BlenderKit Online Asset Library” is probably the problem. If I disable it without uninstalling it and I double-click the problematic blender file, it does not crash. BlenderKit version is 3.11.0.240207. It seems the latest version according to their update checker. If the add-on is not enabled and I go the preferences window to enable it, the moment that I click the checkbox Blender crashes. That is, of course, only for the Blender file with the problematic window configuration. Now, three questions remain to me. 1. Should I report this bug to the BlenderKit creator. 2. Does Blender have some responsibility by letting this add-on crash the whole software at start-up? 3. Why is this problem present only when double-clicking the blend file and not when loading the file through the menu or drag-and-drop? I feel that order that things are loaded when double-clicking the blend file is different from opening Blender and then loading the blend file. Probably that Blender has more time to complete loading a certain module for example and when loading the blender file after, everything is ready to be used. It is such a precise scenario under very specific conditions to crash Blender that it makes me think that the execution is quite convoluted. Edit: I just made another test quickly and I discovered that opening Blender from the start menu (no project), creating a second main window (nothing more and not maximized view in that case) and going to the preferences window and enabling BlenderKit also makes it crash.

ProjectClosesAutomatically3.crash.txt

12 KiB

Pratik Borhade commented

2024-04-10 07:00:33 +02:00

Thanks. Logs captured python311.dll as exception module. Guess the add-on needs some changes to be compatible with 4.1+
I tried to reproduce the crash with blenderkit addon, double clicking ProjectClosesAutomatically3.blend did not trigger the crash though.
@ChengduLittleA , can you confirm on multi-monitor setup?

I think it's best to report crash at blenderkit repo.

Thanks. Logs captured `python311.dll` as exception module. Guess the add-on needs some changes to be compatible with 4.1+ I tried to reproduce the crash with blenderkit addon, double clicking `ProjectClosesAutomatically3.blend` did not trigger the crash though. @ChengduLittleA , can you confirm on multi-monitor setup? I think it's best to report crash at blenderkit repo.

Jesse Yurkovich commented

2024-04-10 07:03:09 +02:00

The exception is coming from the BlenderGIS addon, not blenderkit:

# Python backtrace
  File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 824 in _exhaustive_wait
  File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 895 in wait
  File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 440 in _poll
  File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 257 in poll
  File "C:\Users\Sebastien\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\NodePreview\display.py", line 68 in run
  File "C:\Users\Sebastien\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\BlenderGIS-master\__init__.py", line 117 in run_with_except_hook
  File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\threading.py", line 1045 in _bootstrap_inner
  File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\threading.py", line 1002 in _bootstrap

The exception is coming from the BlenderGIS addon, not blenderkit: ``` # Python backtrace File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 824 in _exhaustive_wait File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 895 in wait File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 440 in _poll File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\multiprocessing\connection.py", line 257 in poll File "C:\Users\Sebastien\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\NodePreview\display.py", line 68 in run File "C:\Users\Sebastien\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\BlenderGIS-master\__init__.py", line 117 in run_with_except_hook File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\threading.py", line 1045 in _bootstrap_inner File "C:\Program Files\Blender Foundation\Blender 4.1\4.1\python\Lib\threading.py", line 1002 in _bootstrap ```

Sebastien Larocque commented

2024-04-10 14:42:29 +02:00

I was not sure if you expected an answer from me. I decided to run other tests based on the BlenderGIS mention. I disabled BlenderGIS. So far, it does not change anything to the problem. Blender crashes precisely when BlenderKit is enabled independently of BlenderGIS.

Based on the crash log, you seem to be able to see an exception from BlenderGIS. I’m not knowledgeable enough concerning the Blender internal behavior to make another decision at this point. I’m just wondering if this could be another add-on or the crash log states precisely the components involved in the crash.

Let me know if you want me to do something.

I was not sure if you expected an answer from me. I decided to run other tests based on the BlenderGIS mention. I disabled BlenderGIS. So far, it does not change anything to the problem. Blender crashes precisely when BlenderKit is enabled independently of BlenderGIS. Based on the crash log, you seem to be able to see an exception from BlenderGIS. I’m not knowledgeable enough concerning the Blender internal behavior to make another decision at this point. I’m just wondering if this could be another add-on or the crash log states precisely the components involved in the crash. Let me know if you want me to do something.

Sebastien Larocque commented

2024-04-11 14:51:09 +02:00

I discovered that this bug might be related to another bug that I reported recently.

Blender closes when the computer hibernates
Reference: #119748

I decided to deactivate the BlenderKit add-on since it appeared to crash Blender. Most of the time, I put my computer in hibernate mode every night after work while leaving my Blender project open to be ready for the next morning. Recently, I discovered that Blender was gone from the task bar as recently mentioned in my bug mentioned report above. Since I deactivated BlenderKit, this problem disappeared (at least on a small number of tests that I did).

Furthermore, I discovered that activating the BlenderKit add-on makes Blender crash automatically even if the view is not maximized in a second main window.

I included the crash log of an empty project I already included in this report. To reproduce the issue and get the crash log:

Open the project “BlandNewProjectMaximizedView.blend” (not by double-clicking).
Go the preferences window.
Enable BlenderKit. If already enabled, you can disable it (uncheck the box) and just re-enable it.
It crashes a second later.
Note that opening Blender from the menu does the same thing. I’m just not sure how it handles crash logs.

Could the two issues be related?

I discovered that this bug might be related to another bug that I reported recently. Blender closes when the computer hibernates Reference: https://projects.blender.org/blender/blender/issues/119748 I decided to deactivate the BlenderKit add-on since it appeared to crash Blender. Most of the time, I put my computer in hibernate mode every night after work while leaving my Blender project open to be ready for the next morning. Recently, I discovered that Blender was gone from the task bar as recently mentioned in my bug mentioned report above. Since I deactivated BlenderKit, this problem disappeared (at least on a small number of tests that I did). Furthermore, I discovered that activating the BlenderKit add-on makes Blender crash automatically even if the view is not maximized in a second main window. I included the crash log of an empty project I already included in this report. To reproduce the issue and get the crash log: - Open the project “BlandNewProjectMaximizedView.blend” (not by double-clicking). - Go the preferences window. - Enable BlenderKit. If already enabled, you can disable it (uncheck the box) and just re-enable it. - It crashes a second later. - Note that opening Blender from the menu does the same thing. I’m just not sure how it handles crash logs. Could the two issues be related?

BlandNewProjectMaximizedView.crash.txt

49 KiB

Sebastien Larocque referenced this issue

2024-04-11 14:59:50 +02:00

Blender closes when the computer hibernates #119748

Sebastien Larocque referenced this issue

2024-04-11 15:03:54 +02:00

Access violation in `vk_icdNegotiateLoaderICDInterfaceVersion` when putting computer to sleep. #112146

Pratik Borhade commented

2024-04-25 06:54:51 +02:00

I think it's best to report the crash to blenderkit developer. Add-on developer will make a report here if they finds the crash out of their scope.

Pratik Borhade closed this issue