Blender crashes on opening file explorer window (Open, Save as, Import, Export) #91149

Closed
opened 2021-09-03 04:50:39 +02:00 by spearit · 18 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96

Blender Version
Broken: version: 2.93.3, branch: master, commit date: 2021-08-17 18:30, hash: 8b80d19f36
Worked: (newest version of Blender that worked as expected)

Short description of error
Whenever I open a file browser window from Blender (e.g.: Export, Import, Open, Save As, etc.), it crashes. For example when I click on File>Open, it seems like many file explorer windows are being opened in quick succession on top of each other until the "Blender File View" titled window appears on top and the program immediately exits. This whole process takes about 3-4 seconds and renders the program unresponsive.

The error occurs when the desktop is extended to my TV (4K TV, Marked by Windows as "Screen 1", set as secondary screen, connected via HDMI through the video card), and the (Export, Import, Open, etc.) file browser window is opened while Blender's window is maximized on "Screen 2" (FullHD monitor, set as the primary screen, connected via DVI-I through the video card).

If Blender is maximized on the extended desktop on the TV, the error will not occur.
If Blender is not maximized on the primary monitor screen, the error will not occur.
If the TV is set as the primary screen, Blender can be maximized on either of the screens and the error will not occur.

Exact steps for others to reproduce the error

  1. Extend Windows desktop so that primary screen is FullHD monitor, while extended screen is 4K TV.
  2. Start Blender
  3. Maximize Blender window on FullHD monitor primary screen.
  4. Click File>Open
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96 **Blender Version** Broken: version: 2.93.3, branch: master, commit date: 2021-08-17 18:30, hash: `8b80d19f36` Worked: (newest version of Blender that worked as expected) **Short description of error** Whenever I open a file browser window from Blender (e.g.: Export, Import, Open, Save As, etc.), it crashes. For example when I click on File>Open, it seems like many file explorer windows are being opened in quick succession on top of each other until the "Blender File View" titled window appears on top and the program immediately exits. This whole process takes about 3-4 seconds and renders the program unresponsive. The error occurs when the desktop is extended to my TV (4K TV, Marked by Windows as "Screen 1", set as secondary screen, connected via HDMI through the video card), and the (Export, Import, Open, etc.) file browser window is opened while Blender's window is maximized on "Screen 2" (FullHD monitor, set as the primary screen, connected via DVI-I through the video card). If Blender is maximized on the extended desktop on the TV, the error will not occur. If Blender is not maximized on the primary monitor screen, the error will not occur. If the TV is set as the primary screen, Blender can be maximized on either of the screens and the error will not occur. **Exact steps for others to reproduce the error** 1. Extend Windows desktop so that primary screen is FullHD monitor, while extended screen is 4K TV. 2. Start Blender 3. Maximize Blender window on FullHD monitor primary screen. 3. Click File>Open
Author

Added subscriber: @spearit

Added subscriber: @spearit

#91229 was marked as duplicate of this issue

#91229 was marked as duplicate of this issue
Author

UPDATE: I played around with the positioning of the Blender window and found the following:

  1. When I dragged the maximized Blender window on the primary monitor screen just a little (by about 20-30 pixels) so it was no longer maximized but still covered almost the whole screen, the error still occurred.
  2. When I tried to reopen Blender and maximize its window, the error did not occur anymore.

My suspicion:

Whenever the error occurs, the file explorer window seems to be stuck in an opening loop touching the top border of the screen. When the error does not occur, the explorer window opens around the middle of the screen. Playing around with the position of the main Blender window may have affected the coordiantes where Blender opens the file explorer window, hence avoiding the trigger for the error.
blender crash1.png blender crash2.png

UPDATE: I played around with the positioning of the Blender window and found the following: 1. When I dragged the maximized Blender window on the primary monitor screen just a little (by about 20-30 pixels) so it was no longer maximized but still covered almost the whole screen, the error still occurred. 2. When I tried to reopen Blender and maximize its window, the error did not occur anymore. My suspicion: Whenever the error occurs, the file explorer window seems to be stuck in an opening loop touching the top border of the screen. When the error does not occur, the explorer window opens around the middle of the screen. Playing around with the position of the main Blender window may have affected the coordiantes where Blender opens the file explorer window, hence avoiding the trigger for the error. ![blender crash1.png](https://archive.blender.org/developer/F10364512/blender_crash1.png) ![blender crash2.png](https://archive.blender.org/developer/F10364513/blender_crash2.png)
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Hi, thanks for the report. No crash here when I set my secondary display to TV.

Can you please attach the crash logs?: https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#crash-log

Steps I followed:

  • Extend the screen (secondary screen: TV)
  • Maximize window (Window -> Toggle window FullScreen
  • File -> Open

Can you please mention the arrangement of the windows?
image.png

Hi, thanks for the report. No crash here when I set my secondary display to TV. Can you please attach the crash logs?: https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#crash-log Steps I followed: - Extend the screen (secondary screen: TV) - Maximize window (`Window -> Toggle window FullScreen` - `File -> Open` --- Can you please mention the arrangement of the windows? ![image.png](https://archive.blender.org/developer/F10364828/image.png)
Member

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

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

Hi, thanks for looking into the issue.

Here are the logs after a crash: blender.crash.txt

Also, this is the arrangement in use:
kép.png

Please let me know, if I can help you with more info.

Hi, thanks for looking into the issue. Here are the logs after a crash: [blender.crash.txt](https://archive.blender.org/developer/F10375115/blender.crash.txt) Also, this is the arrangement in use: ![kép.png](https://archive.blender.org/developer/F10375118/kép.png) Please let me know, if I can help you with more info.
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

Can you also test this with 3.0? It has a fix when multiple windows are in a vertical arrangement, and wondering if this might matter for you with such a difference in the tops and bottoms of your two. We have that patch in a list of things to possibly backport to 2.93. So it would be awesome if you could test it. If it does nothing for you then we also know that this is not related.

Can you also test this with 3.0? It has a fix when multiple windows are in a vertical arrangement, and wondering if this might matter for you with such a difference in the tops and bottoms of your two. We have that patch in a list of things to possibly backport to 2.93. So it would be awesome if you could test it. If it does nothing for you then we also know that this is not related.
Member

@spearit wrote:
Also, this is the arrangement in use:
kép.png

You said #1 is 4K, so 3,840 x 2,160? And #2 is 1920 x 1080? What is the Windows OS "Scale" of each? ie, are they both at 100% or do you set one higher?

When you extend your monitors like this you get a virtual desktop like the following, which is a little unusual:

desktop.png

Why do you have the bottom of #2 below that of #1? Does it make any difference if you drag that one up?

>@spearit wrote: > Also, this is the arrangement in use: > ![kép.png](https://archive.blender.org/developer/F10375118/kép.png) You said #1 is 4K, so 3,840 x 2,160? And #2 is 1920 x 1080? What is the Windows OS "Scale" of each? ie, are they both at 100% or do you set one higher? When you extend your monitors like this you get a virtual desktop like the following, which is a little unusual: ![desktop.png](https://archive.blender.org/developer/F10375206/desktop.png) Why do you have the bottom of #2 below that of #1? Does it make any difference if you drag that one up?
Member

Added subscriber: @Eligecos

Added subscriber: @Eligecos
Author

You said #1 is 4K, so 3,840 x 2,160? And #2 is 1920 x 1080? What is the Windows OS "Scale" of each? ie, are they both at 100% or do you set one higher?

When you extend your monitors like this you get a virtual desktop like the following, which is a little unusual:

desktop.png

Why do you have the bottom of #2 below that of #1? Does it make any difference if you drag that one up?

  1. Screen arrangement and resolutions are as you say. However, #1 scale is at 225% to make up for the small icons on the 4K screen. The fullHD screen's scale is at 100%.
  2. The screen arrangement represents how my TV and the monitor screens are positioned in the real world. As such, the mouse cursor passage between the two is accurately aligned.
  3. I have downloaded and run Blender 3.0 to test it and it does not produce the error. Note though, that this time I cannot reproduce the errror even when using Blender 2.9xx. AFAIK I did not made changes to the system.
> You said #1 is 4K, so 3,840 x 2,160? And #2 is 1920 x 1080? What is the Windows OS "Scale" of each? ie, are they both at 100% or do you set one higher? > > When you extend your monitors like this you get a virtual desktop like the following, which is a little unusual: > > ![desktop.png](https://archive.blender.org/developer/F10375206/desktop.png) > > Why do you have the bottom of #2 below that of #1? Does it make any difference if you drag that one up? 1. Screen arrangement and resolutions are as you say. However, #1 scale is at 225% to make up for the small icons on the 4K screen. The fullHD screen's scale is at 100%. 2. The screen arrangement represents how my TV and the monitor screens are positioned in the real world. As such, the mouse cursor passage between the two is accurately aligned. 3. I have downloaded and run Blender 3.0 to test it and it does not produce the error. Note though, that this time I cannot reproduce the errror even when using Blender 2.9xx. AFAIK I did not made changes to the system.
Member

@spearit - Thanks for the details. And I certainly appreciate any help you can provide to help with this.

2.93 was our first version where windows (parent or child) are saved and loaded in a way that works properly on multiple monitors on the Windows platform. Before that Blender would also just launch on the main monitor and any children would open in the same monitor as the parent.

This worked great when monitors were arranged horizontally but exposed an issue when there was a vertical disparity between them, especially if any are above any others. This was fixed in 3.0 and is now backported to 2.93 for the next LTS release of that line. Should be 2.93.5

3.0 is also our first version where placement of windows will also take into account the increased size of window chrome when you set the OS scaling higher than 100% - the titlebar gets wider, which impacts on the calculation of its location. That could also possibly affect you here too.

So I am glad you are not seeing the issue with 3.0, but can't really pinpoint this problem unless you see it again in 2.93 so keep us posted.

@spearit - Thanks for the details. And I certainly appreciate any help you can provide to help with this. 2.93 was our first version where windows (parent or child) are saved and loaded in a way that works properly on multiple monitors on the Windows platform. Before that Blender would also just launch on the main monitor and any children would open in the same monitor as the parent. This worked great when monitors were arranged horizontally but exposed an issue when there was a vertical disparity between them, especially if any are above any others. This was fixed in 3.0 and is now backported to 2.93 for the next LTS release of that line. Should be 2.93.5 3.0 is also our first version where placement of windows will also take into account the increased size of window chrome when you set the OS scaling higher than 100% - the titlebar gets wider, which impacts on the calculation of its location. That could also possibly affect you here too. So I am glad you are not seeing the issue with 3.0, but can't really pinpoint this problem unless you see it again in 2.93 so keep us posted.

Added subscriber: @Garek

Added subscriber: @Garek

@spearit hi, can you update us on this?
Did you catch issue again on 2.93 (prior to 2.93.5)?
Can you check latest 3.1.0 alpha to see if issue is here?
https://builder.blender.org/download/daily/

@spearit hi, can you update us on this? Did you catch issue again on 2.93 (prior to 2.93.5)? Can you check latest 3.1.0 alpha to see if issue is here? https://builder.blender.org/download/daily/
Author

@Garek , I have been using Blender 2.93.3 with the above described display configuration and as far as I remember there were maybe one or two occasions when the error happened. Since it was so rare and I could not reproduce them, I did not bother to report them. I am not aware of any changes that I made to my system, which may have caused the error to occur fewer times.

Now I downloaded 3.1.0 alpha and clicked around in an effort to summon the error, but it has not reared its head, so it seems the alpha is either more resistant or completely immune to it under my screen configuration.

@Garek , I have been using Blender 2.93.3 with the above described display configuration and as far as I remember there were maybe one or two occasions when the error happened. Since it was so rare and I could not reproduce them, I did not bother to report them. I am not aware of any changes that I made to my system, which may have caused the error to occur fewer times. Now I downloaded 3.1.0 alpha and clicked around in an effort to summon the error, but it has not reared its head, so it seems the alpha is either more resistant or completely immune to it under my screen configuration.

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

Changed status from 'Needs User Info' to: 'Resolved'
Garek closed this issue 2022-01-22 16:59:50 +01:00
Garek self-assigned this 2022-01-22 16:59:50 +01:00

Thanks for an answer. I think it's better to close this task then. If this issue will appear again in 3.1.0 let us know there.

Thanks for an answer. I think it's better to close this task then. If this issue will appear again in 3.1.0 let us know there.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#91149
No description provided.