Slow start of Blender 4.0.1 and 4.0.2 #115935
Labels
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
13 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#115935
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Windows 10, latest updates installed, AMD 2600, 64 gb RAM, GPU Nvidia GTX 3070TI, Latest driver for GPU is installed.
Blender 4.0.2
When starting Blender 4.0, is takes quite a long time (35+ seconds) before the splash screen appears. In very,very rare cases, the splash screen appears within 8 seconds (what I expect considering previous versions). Blender 3.6.4 on the same system does not show this behaviour.
I did remove all add-ons and started with "factory" settings,, this does not make any difference.
I did start Blender 4.0 with debug cmd file, but in the log file there was nothing obvious. Is this a known problem for certain environments ?
No errors seen
When blender is started, everything is working fine, with of without add-ons.
Perhaps you have some network/cloud drive attached that may take too much time to access? Did any previous version start fast?
Hi, really thanks for you reactions. Previous versions (3.3.1, 3.5.1, 3.6.4) do start as expected (around 6-8 seconds before splash screen appears).
Attachted the system-info.txt file
I have a cloud drive (onedrive) attached, but opening folders on this drive seems to happen without delay.
In the mean time, I've uninstalled onedrive, rebooted several times, but no change in startup times (which are pretty consistent after reboot )
time unill splashscreen with
3.3.1 - 5 seconds
3.5.1 - 6 seconds
3.6.4 - 7 seconds
4.0.1 and 4.0.2 - 36 seconds (and after several reboots and doing this same sequence, I once saw 8 seconds for 4.0 ???, but then without reboot and restart 4.0, again 36 seconds, and subsequent reboots again, results in a consistent 36 seconds for starting 4.0)
Thanks for update. Please download alpha build from https://builder.blender.org/download/daily/ and check if this happens as well.
If it does, run file
factory_startup.cmdand check if that takes a long time too.Okay, downloaded and started 4.1 alpha several times, first time start was 32 seconds.
Then rebooted, started and closed first 3.3.1, then 3.5.1, then 3.6.4, all around 5-7 seconds, then started 4.1, ehmmm, 3 (!) seconds for splash screen, hurray you might think, but reboot again, and do this same sequence again, 4.1 = 32 seconds, and reboot again, and just start 4.1 at first, 32 seconds again. 4.1 started everytime with blender_factory_startup.cmd.
Attached are 3 log files, where the one with "fast" in the name, was the one with the 3 seconds startup).
Weird huh ?
That is indeed weird, but I am afraid I won't be able to help much. Given, that there have been no reports about this, it suggests this is caused by something specific to your setup.
Now this probably highly depends on HW, but even 3.x startup times are quite high. On my machine it takes about 0.5s to startup Even my backup machine needs max 2 seconds.
Hi Richard, oke, sounds plausible that it is something specific to my setup. In the mean time I've been changing configs and software on my system, and there is at least one thing which helps consistently, disconnect PC from my network/internet. When I have no network active, Blender 4.0 starts within 2-4 seconds (which is normal for me on my system). And it definitely is somewhere a delay of 30 seconds, when I measure the startup times with network (33-35 seconds). When I switch of network discovery, so no other devices or so are seen/discoverd, but with internet active, startup times are also long. And previous versions of Blender do no show this, so it seams also something specific to 4.0.
And yes, did also another test, I created a new user under windows, and only installed blender 4.0 for that user, networking as normal, and Blender 4 works as expected, startup within 4 seconds. So it looks like something in my user profile in combi with blender 4.0 causes this, but I really can't find what ?
At this point, if you really want to find issue, you would have to either compile Blender from sources and pause debugger while it is still loading.
If the issue is network, there is good chance, that there have been some change in filebrowser code, but I would expect more reports then.
Alternative is to start setting up new user, until you encounter this issue again. But there is chance that you won't be able to reproduce it. My guess would be onedrive you have mentioned.
I'm experiencing this slow start as well in the recents 4.1 builds... but it's very random, sometimes it loads fast, sometimes it take ages... hard to tell why that happens (no network/cloud drive attached here)... 😕
Thanks again Richard, I'am gonna setup a new user and take it from there. If i find a cause, i will report it back. In the mean time no further actions on this ticket is needed
Hi, I've seen similar issue people reporting on 3.6, 4.0: #115806, #114247, #115008
Cause is not clear to us yet. As you said, network connection increased the startup time which points to add-on (like blenderkit), script as culprit. But I guess you're experiencing this issue with factory settings as well.
Can I ask for your userprefs.blend file?
C:\Users\user_name\AppData\Roaming\Blender Foundation\Blender\4.0\config\Hi Pratik, yes, I tested with factory settings as well, and also without any addons installed, but situation stays the same. Very rarely, blender 4 starts fast (3-5 seconds), in 99% of the cases startup time is long (35+ seconds).
Attached my userpref.blend file used.
As mentioned before, I created a new user under windows now (for testing purposes), and using then blender 4.0 (or 3.6.4), everything is fast (with same addons installed as for the "original" user).
I've had similar slow starts from Blender 4.0.1 and now 4.0.2. I've attached my system info in case that helps.
Diagnosing this a bit more locally it does seem related to Blender trying to access parts of my network that for some reason take a lot of time. When I disable my ethernet connector and then start Blender, it starts in a few seconds. When I enable it again, it takes over 30 seconds. The titlebar in that case reads "* (Unsaved)" for a long time and then switches to "(Unsaved)" when it shows the splash screen.
Using sysinternals procmon64 to capture all file access during startup of Blender showed me that it was accessing a few network paths that no longer existed (as that server was turned off). It took me a while to figure out where they were, but I had them in my "Quick access" list in File Explorer. Removing (unpinning) them there solved the issue. Blender starts quickly again! Might be worth exploring for you too @William-de-Bie
Hi Marcel, that is exactly the same situation I have. As a quick test, you could create a new windows user, and start blender 4.0 logged in with that new user ( just start blender.exe from the installed blender folder). It is not the solution, but indicates it is something in the user profile and network in combination with blender 4.0. Blender 3.6.4 and earlier versions don't do this.
Yeah, removing those network drives from my "Quick access" list did the trick. At least this means you have something to look for in your user profile now. Happy hunting! :)
I already removed all network drives and cloud drives before,and that did not help, BUT, in the "quick access" area, there was indeed still a link to a network drive (in unc format e.g. \192.168.xxx.xx\path$) which was not online.
Unpin and remove from the quick access helped ! Many thanks @Marcel-Offermans
I have the very same issue. However, no network drives, nothing in the Quick Access. I tried removing addons one by one, tried different fresh installments, running with factory settings, disabling Firewall, WindowsDefender and disconnecting from the Internet. I also tried three different PCs with Win 10 and 11. Behaviour remains the same: first start takes ages, subsequent starts are fast.
I managed to reproduce it only by messing around with userpref.blend: you can backup the file before running Blender for the first time, then start Blender (here's the slow start) and exit (or just save user preferences). Usually, subsequent starts are fast. However, when you replace the new file with backupped one, you experience the slow start again without rebooting PC.
Also, amount of addons enabled affects the delay: clean blender start takes 7s (first time), then 2s. Blender with addons (my usual work setup) takes 30s to start, then 3s.
Do you mean quick access in windows explorer? @Harley are you aware of this issue?
Yes, I think this all might be a good reason to remove the quick access items from our File Browser lists. It seems like such a nice feature, but we just can't do much about users who have saved network resources to Quick Access and later disconnect those resources. I'd hate to get rid of this but not sure there is a choice. User can always just bookmark things they way. What do you think?
Yes, that is exactly what I mean.
I'm not familiar with the details of how you create your file browser, but it sounds like you could consider to fetch those quick access items asychronously? This is probably caused by one of the items doing a network call which simply blocks until it times out. Such I/O should ideally be done in a separate thread. That way you would not have to get rid of them, it might just take a bit longer for them to appear (but since this is just in the first 30 seconds of Blender running, I don't think many would notice).
@Harley I would expect there to be way to avoid this issue in few ways:
Presumably Explorer itself knows how to enumerate/list these entries without incurring a cost (enough to at least put their names in the quick access list). Otherwise the users would notice that as well. Maybe there's another API we can use on our side?
I assume, that explorer just pulls these from registry or whatever DB. But it's not uncommon, that clicking on inaccessible network path would do nothing, and you got error message after 30 seconds. And if you were me, sometimes you would be even surprised by it and wonder what caused it :D
Explorer has a distinctly different lifetime model than we do, if it spends 30 seconds or so to enumerate those at startup in a background thread most people aren't gonna notice all that much as its "just the computer starting up"
if we want to keep the quick access list, enumerating in the background would likely be our best bet.
I have encountered some network timeout times as along as 10 second per item, and without a way of the program to do anything about that.
For example you can have a big network built properly that has a DNS. You turn off any computer or network resource and you know about its existence of lack thereof almost instantly when you try using that path.
But then you can go to a crappy peer-to-peer network and those just use peer broadcasting to resolve resource. Setups like that can take many multiple seconds per item. And it gets worse when you bind multiple protocols in peer networks as it will wait for all of them.
Since the commit
81017772f5was made, could this situation have improved somehow?Please try the latest daily build: https://builder.blender.org/download/daily/
I don't think that fix will be related here, in that I'm not seeing
BLI_file_alias_targetbeing hit during startup.Or there is a similar error in
fsmenu_add_windows_quick_access, but so far not seeing it.Hi - Just wanted to add my two cents here. I am having the same problem across multiple machines. Blender can take 30 seconds or more to load. (using Blender 4.0.2 on Windows)
If I unplug my desktop from ethernet or put my laptop in Airplane mode, the problem goes away and Blender loads in 3-4 seconds.
So there must be something it is doing network wise at startup that is causing it to hang. Perhaps it is doing a new version check and that is slow or hanging? (does it even do this? I was not notified a new version had come out by the app). Not sure what all its doing reaching out over the network on startup, but it seems that being connected and not "offline" is what causes this problem.
I had the same problem when opening projects, changing views, and changing any property. I disabled the addon RealCity and it fixed all my problems. I hope it helps someone.