blender/blender
159
504
Fork 761
Code Issues 6.8k Pull Requests 912 Projects 18 Wiki Activity

Blender hangs for multiple minutes when opening blend file from networked drive #116675

New Issue
Closed
opened 2023-12-31 18:16:41 +01:00 by Alex Kelly · 13 comments
Alex Kelly commented 2023-12-31 18:16:41 +01:00
Copy Link

System Information
Operating system: Windows 11
Graphics card: EVGA RTX 3090

Blender Version
Broken: 3.6, 4.0.1, 4.0.2
Worked: N/A

Short description of error
Whenever a .blend file is opened from a networked drive (over a VPN or on the network), it hangs (grey screen with "not responding") for multiple minutes until the file loads (this also applies to file browser).

To add some context, I copied all of my files and assets from an external SSD to a NAS drive that is now networked. What I believe is happening is Blender is trying to reference my external SSD, even though all needed files are present in the NAS drive, since it is a carbon copy.

I purged my startup file, then made a new file, and saved it to the NAS. No issue. However, when I append in an asset from the NAS drive into that same file, the problem is back. There is nothing missing from the asset itself (mesh, textures, etc.), but it still makes the file take 3-5 minutes to start up.

Additionally, when the external SSD is plugged into the machine, the file loads up quickly.

Exact steps for others to reproduce the error
Open any .blend file from a networked drive

**System Information** Operating system: Windows 11 Graphics card: EVGA RTX 3090 **Blender Version** Broken: 3.6, 4.0.1, 4.0.2 Worked: N/A **Short description of error** Whenever a .blend file is opened from a networked drive (over a VPN or on the network), it hangs (grey screen with "not responding") for multiple minutes until the file loads (this also applies to file browser). To add some context, I copied all of my files and assets from an external SSD to a NAS drive that is now networked. What I believe is happening is Blender is trying to reference my external SSD, even though all needed files are present in the NAS drive, since it is a carbon copy. I purged my startup file, then made a new file, and saved it to the NAS. No issue. However, when I append in an asset from the NAS drive into that same file, the problem is back. There is nothing missing from the asset itself (mesh, textures, etc.), but it still makes the file take 3-5 minutes to start up. Additionally, when the external SSD is plugged into the machine, the file loads up quickly. **Exact steps for others to reproduce the error** Open any .blend file from a networked drive
Alex Kelly added the
Severity
Normal
Type
Report
Status
Needs Triage
 labels 2023-12-31 18:16:42 +01:00
Pratik Borhade commented 2024-01-01 05:31:56 +01:00
Member
Copy Link

Hi, thanks for the report. This is possibly related to #112599 / #115935 . Can you check?
Did I understand correctly that long startup time is observed when asset library paths are referenced in preferences?

Hi, thanks for the report. This is possibly related to #112599 / #115935 . Can you check? Did I understand correctly that long startup time is observed when asset library paths are referenced in preferences?
Pratik Borhade added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2024-01-01 05:32:05 +01:00
Alex Kelly commented 2024-01-01 06:29:02 +01:00
Author
Copy Link

This does appear to be in the same vein of #115935, however, the blend file is being loaded from a networked drive.

I do believe it is trying to reference an unreachable drive (the external ssd that I coped all of my files off of). Though even when I remove all reference to that drive in asset library paths in preferences, the issue still occurs. I also removed all bookmarks and quick access items that may have been pointing to the old drive, but the issue still occurs in existing files.

This does appear to be in the same vein of #115935, however, the blend file is being loaded from a networked drive. I do believe it is trying to reference an unreachable drive (the external ssd that I coped all of my files off of). Though even when I remove all reference to that drive in asset library paths in preferences, the issue still occurs. I also removed all bookmarks and quick access items that may have been pointing to the old drive, but the issue still occurs in existing files.
Pratik Borhade added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2024-01-01 10:08:48 +01:00
Pratik Borhade commented 2024-01-02 07:04:56 +01:00
Member
Copy Link

Thanks. Can you launch blender from blender_factory_startup.cmd batch file then see whether it still occurs?

but the issue still occurs in existing files.

Does it mean issue is occurring in specific files and not observable when default startup file is opened from blender.exe/blender-launcher.exe?
Also, is blender installed locally or in network drive?

Maybe we can launch a package so you will be able to test #116692

Thanks. Can you launch blender from `blender_factory_startup.cmd` batch file then see whether it still occurs? > but the issue still occurs in existing files. Does it mean issue is occurring in specific files and not observable when default startup file is opened from blender.exe/blender-launcher.exe? Also, is blender installed locally or in network drive? Maybe we can launch a package so you will be able to test https://projects.blender.org/blender/blender/pulls/116692
Pratik Borhade added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2024-01-02 07:05:07 +01:00
Alex Kelly commented 2024-01-02 15:24:00 +01:00
Author
Copy Link

Launching blender from the blender_factory_startup.cmd batch file does not have an issue with initial load times, however I still have issues with load times in the file explorer.

It appears after I deleted references to the unreachable drive, the problem (of long startup times) no longer occurs in the default startup files.

By "existing file", I mean any .blend file that was created before I migrated my data from the external SSD to the NAS networked drive. In addition to this, if I append any asset from an "existing file" to a new file that does not have the issue, it will make the issue present when saved.

Also, is blender installed locally or in network drive?

No, Blender is installed on a local drive in my system.

Launching blender from the blender_factory_startup.cmd batch file does not have an issue with initial load times, however I still have issues with load times in the file explorer. It appears after I deleted references to the unreachable drive, the problem (of long startup times) no longer occurs in the default startup files. By "existing file", I mean any .blend file that was created before I migrated my data from the external SSD to the NAS networked drive. In addition to this, if I append any asset from an "existing file" to a new file that does not have the issue, it will make the issue present when saved. > Also, is blender installed locally or in network drive? No, Blender is installed on a local drive in my system.
Pratik Borhade commented 2024-01-03 05:38:57 +01:00
Member
Copy Link

Thanks, it's clear now. Have you checked whether "existing file" has missing linked library/asset references.
Can you share "existing file"? If you make copy of "existing file" on SSD, it loads in less time, right?

@mano-wii may able to investigate it since he is involved in similar reports already

Thanks, it's clear now. Have you checked whether "existing file" has missing linked library/asset references. Can you share "existing file"? If you make copy of "existing file" on SSD, it loads in less time, right? @mano-wii may able to investigate it since he is involved in similar reports already
Timothy Cook commented 2024-01-03 06:15:55 +01:00
Copy Link

I just want to possibly confirm this bug.
I network through my router a folder that I keep on the desktop of both my PC and my Mac to make file transfers quick and seamless.
I just started using this for Blender files and noticed that anytime I tried to view the Desktop, where I keep the networked folder, through Blender's File Browser that it would hang Blender. I thought this was a soft crash happening so I would just force quit Blender.

Looks like there is a fix going out. I hope it trickles down to 3.6

I just want to possibly confirm this bug. I network through my router a folder that I keep on the desktop of both my PC and my Mac to make file transfers quick and seamless. I just started using this for Blender files and noticed that anytime I tried to view the Desktop, where I keep the networked folder, through Blender's File Browser that it would hang Blender. I thought this was a soft crash happening so I would just force quit Blender. Looks like there is a fix going out. I hope it trickles down to 3.6
Alex Kelly commented 2024-01-03 19:47:12 +01:00
Author
Copy Link

Can you share "existing file"? If you make copy of "existing file" on SSD, it loads in less time, right?

I can share "existing file" though it is a bit large (1gb). It is a stark example of the issue, though, because when opening from the networked drive it takes ~8minutes 6seconds. On a local ssd, however, it only takes 7ish seconds.

Have you checked whether "existing file" has missing linked library/asset references.

I went through the file, and it should not have any references to missing library/assets.

> Can you share "existing file"? If you make copy of "existing file" on SSD, it loads in less time, right? I can share "existing file" though it is a bit large (1gb). It is a stark example of the issue, though, because when opening from the networked drive it takes ~8minutes 6seconds. On a local ssd, however, it only takes 7ish seconds. > Have you checked whether "existing file" has missing linked library/asset references. I went through the file, and it should not have any references to missing library/assets.
Pratik Borhade commented 2024-01-04 05:14:02 +01:00
Member
Copy Link

Ok, is it possible to narrow down the file so we can use it locally to investigate?
Also 81017772f5 is merged now, so please check if this is still an issue in 4.1: https://builder.blender.org/download/daily/

Ok, is it possible to narrow down the file so we can use it locally to investigate? Also 81017772f5257082e71a525fab78aeac7c8bbf47 is merged now, so please check if this is still an issue in 4.1: https://builder.blender.org/download/daily/
Germano Cavalcante commented 2024-01-04 15:21:04 +01:00
Member
Copy Link

@BB12, since 81017772f5 was committed, can you check if this issue was fixed in latest daily build?
https://builder.blender.org/download/daily/

@BB12, since 81017772f5 was committed, can you check if this issue was fixed in latest daily build? https://builder.blender.org/download/daily/
Timothy Cook commented 2024-01-04 19:53:39 +01:00
Copy Link

I just tested with 4.1 and no longer have the issue of Blender freezing when viewing the shared networked folder with Blender's File Browser.

Thanks!

I just tested with 4.1 and no longer have the issue of Blender freezing when viewing the shared networked folder with Blender's File Browser. Thanks!
Germano Cavalcante commented 2024-01-04 20:27:23 +01:00
Member
Copy Link

Glad to know. Thanks :)

Glad to know. Thanks :)
Blender Bot added
Status
Archived
 and removed
Status
Needs Information from User
 labels 2024-01-04 20:27:30 +01:00
Timothy Cook commented 2024-01-04 20:31:35 +01:00
Copy Link

@mano-wii
I want to add that I'm not the original author of this bug report though so you may not want to close it if it is still n issue for them.

@mano-wii I want to add that I'm not the original author of this bug report though so you may not want to close it if it is still n issue for them.
Alex Kelly commented 2024-01-05 02:10:38 +01:00
Author
Copy Link

Hello, apologies for the delayed response!

I believe this does indeed fix the described problem. It is still a bit slow on my end, but I believe that is due to networking issues that are separate from Blender.

I'm glad a fix was reached!

Hello, apologies for the delayed response! I believe this does indeed fix the described problem. It is still a bit slow on my end, but I believe that is due to networking issues that are separate from Blender. I'm glad a fix was reached!
❤️ 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Code Documentation
Code comments, Python/RNA API descriptions

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
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
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, see policy: https://developer.blender.org/docs/handbook/bug_reports/vulnerability_reports/

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
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

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
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

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 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#116675
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?