Blender File View Unresponsive When Accessing Desktop #99859

New Issue

BMan · 2022-07-20T05:07:37+02:00

BMan commented

2022-07-20 05:07:37 +02:00

System Information
Operating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.26

Blender Version
Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac
Worked: Unknown, this issue goes back to at least 2.83.9

Short description of error
Blender File View becomes unresponsive for an average of 20-30 seconds when accessing Desktop. During this time, the file view is blank and the window can not be closed. Open, Save, Save As, Save Copy under the File menu or Open function in Image Texture node or Texture Properties all produce the same result. Saving a file, creating, deleting and renaming a folder inside Blender File View all create the same unresponsive blank screen.

Exact steps for others to reproduce the error
Any of these actions: Access Desktop. Create, rename, delete folder. Save file.
Based on the default startup.

**System Information** Operating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.26 **Blender Version** Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: `a2d59b2dac` Worked: Unknown, this issue goes back to at least 2.83.9 **Short description of error** Blender File View becomes unresponsive for an average of 20-30 seconds when accessing Desktop. During this time, the file view is blank and the window can not be closed. Open, Save, Save As, Save Copy under the File menu or Open function in Image Texture node or Texture Properties all produce the same result. Saving a file, creating, deleting and renaming a folder inside Blender File View all create the same unresponsive blank screen. **Exact steps for others to reproduce the error** Any of these actions: Access Desktop. Create, rename, delete folder. Save file. Based on the default startup.

BMan commented

2022-07-20 05:07:37 +02:00

Added subscriber: @bassomatic76

Omar Emara commented

2022-07-20 08:48:40 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-07-20 08:48:40 +02:00

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

Omar Emara commented

2022-07-20 08:48:40 +02:00

Do you have any network devices connected that might cause the holdup? Does the Desktop have any special files/symbolic links/large images/or other non standard files?
It only happens for the Desktop directory, correct?

Do you have any network devices connected that might cause the holdup? Does the Desktop have any special files/symbolic links/large images/or other non standard files? It only happens for the Desktop directory, correct?

BMan commented

2022-07-21 08:37:36 +02:00

No network devices connected. The Desktop isn't shared or backed up to Dropbox or anything like that. The Desktop did have alias files (Mac versions of symlinks) and many large .dmg, .iso files. Removing these didn't fix the issue. However...

Short Explanation:
An alias to a shared computer on the network seems to cause the issue no matter what folder the alias is in. Regular aliases and large files don't seem to affect Blender at all. This seems to be an issue with alias files that point to shared network machines.

Long Explanation:
Your questions prompted me to use an empty Desktop (something that isn't usually in my workflow) and I found the one file type that is causing the unresponsiveness, no matter what folder it is in.

The culprit seems to be an alias to another shared computer on the network. It is the only alias of it's type and has only ever been on the Desktop, which is why this appeared at first to be a Desktop issue.

Blender seems to be activating the alias somehow when it lists the folder that contains it and an attempt to connect to the shared machine occurs. (No other programs seem to do this.) The shared computer isn't available on the network and the process times out eventually allowing Blender to continue.

It seems this activation of the alias occurs every time Blender accesses the folder containing the alias or when a file is saved or a folder is created, deleted or renamed.

No network devices connected. The Desktop isn't shared or backed up to Dropbox or anything like that. The Desktop did have alias files (Mac versions of symlinks) and many large .dmg, .iso files. Removing these didn't fix the issue. However... Short Explanation: An alias to a shared computer on the network seems to cause the issue no matter what folder the alias is in. Regular aliases and large files don't seem to affect Blender at all. This seems to be an issue with alias files that point to shared network machines. Long Explanation: Your questions prompted me to use an empty Desktop (something that isn't usually in my workflow) and I found the one file type that is causing the unresponsiveness, no matter what folder it is in. The culprit seems to be an alias to another shared computer on the network. It is the only alias of it's type and has only ever been on the Desktop, which is why this appeared at first to be a Desktop issue. Blender seems to be activating the alias somehow when it lists the folder that contains it and an attempt to connect to the shared machine occurs. (No other programs seem to do this.) The shared computer isn't available on the network and the process times out eventually allowing Blender to continue. It seems this activation of the alias occurs every time Blender accesses the folder containing the alias or when a file is saved or a folder is created, deleted or renamed.

Omar Emara commented

2022-07-21 08:46:22 +02:00

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

Omar Emara commented

2022-07-21 08:46:22 +02:00

Okay, I will leave this to someone on Mac to reproduce.

Harley Acheson commented

2023-03-14 00:37:46 +01:00

When Blender lists the contents of a folder that contains any Mac aliases it DOES ask the operating system for the target of that alias. This is just part of our routines because we cache file listing results for increased performance. If we don't ask for alias targets during listings we'd need to do so later, when it is accessed and every time, making it slower for people who use many of them.

The problem here seems to be that you have an alias to a computer that "isn't available on the network". I would expect your OS to interrogate such a machine to see if it is just sleeping, wait for a timeout for it to wake up, and then respond that it is unavailable.

My only suggestion would be to put such an alias in a folder so it does not have to be accessed when you use Blender to browse your desktop.

When Blender lists the contents of a folder that contains any Mac aliases it DOES ask the operating system for the target of that alias. This is just part of our routines because we cache file listing results for increased performance. If we don't ask for alias targets during listings we'd need to do so later, when it is accessed and every time, making it slower for people who use many of them. The problem here seems to be that you have an alias to a computer that "isn't available on the network". I would expect your OS to interrogate such a machine to see if it is just sleeping, wait for a timeout for it to wake up, and then respond that it is unavailable. My only suggestion would be to put such an alias in a folder so it does not have to be accessed when you use Blender to browse your desktop.

👍 1

BMan commented

2023-03-14 00:51:21 +01:00

Indeed, removing the link to a folder I do not use for Blender has been the solution. Thanks!

BMan closed this issue

2023-03-14 00:51:23 +01:00

Blender Bot added

and removed

labels 2023-03-14 00:51:24 +01:00

Harley Acheson commented

2023-03-14 00:54:00 +01:00

@bassomatic76 - Awesome. Thanks.

Sorry for the delay in checking in with this, but I was going through older reports and wanted to make sure all is okay.

I'll close this now, but feel free to open a new report if need be.

@bassomatic76 - Awesome. Thanks. Sorry for the delay in checking in with this, but I was going through older reports and wanted to make sure all is okay. I'll close this now, but feel free to open a new report if need be.

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 File View Unresponsive When Accessing Desktop #99859