I recently noticed that after loading a (larger, around 9 GB) scene, the status bar (green bar on the Blender icon in the Windows task bar, that usually starts going during startup, rendering etc) keeps slowly moving for several minutes.
I’m in solid shading, so it’s not compiling shaders.
I’m guessing the scene shows as being loaded though it’s not yet fully loaded? Or is Blender still loading addons? There are… many. The AB is not opened in the bottom.
Just trying to figure this out so I can maybe setup/optimize my Cleanpanels addon, which can “lazy load” addons.
The data saved in the file is not what is used in any app on runtime… also if the file was compressed then it proberly has to do some decompressiong first.
So if the file itself is 9GB and this reorganization of data or decompression is done and for example you only have 16GB then there is a lot of data shoveling in the work. Even with 32GB most people just do use more programs in parallel and so…
I have 128 GB and 49% are used in total, so memory shouldn’t be an issue.
I was just wondering, because I assumed I would only be able to access the UI once the file was fully loaded & processed. That’s why I wanted to find out about the succession of processes during/after loading - any - file.
I venture to suppose that the actual answer might be somewhere in your questions. If your scene is really that large (circa 9gb) that comes along with a lot of add-ons then, in my opinion, it’s no wonder why these “glitiches” could manifest.
As for you RAM size, I may be wrong since I have only 16 of it on my board, perhaps Blender doesn’t use it to the fullest or something like that? Just curious.
Blender is at runtime holding data that will quite likely not be written into the file cause its sort of redundant and would just blow up the stored filesize, things like the bvh tree or the bmesh datastructures of meshes. Their rebuilt might get triggered after load. Beside that addons can also hook up and do neccessary stuff on post_load. So yeah loading the data from disk isnt neccessarily the end of the work that needs to be done. And you are just experiencing it cause the file is so large, and as a whole it consumes quite measurables amounts of time then.
See, I ddn’t think of that: it’s probably loading linked assets’ materials etc., even though they’re already visible in the VP!
The strange thing is I can even render it on GPU (8 GB, @Okidoki - LAME! Just like my Dual Silver Xeons, but I didn’t have THAT much money back then), so maybe I finally did something right this time. Interface is always locked - I don’t have any problems rendering the thing, just the long post loading process got me curious. And with my brain switched on, it seems somewhat logical
@goorman I have previously rendered projects that required almost 400 GB RAM and I hadn’t had enough scratch disk available, so Blender crashed as soon as the 128 GB RAM were used up. But back then, it’s very likely I did things the wrong way, had to send the file to a render farm and made instances of a large landscape scatter real and then restored an auto save from that one or so. So Blender does gobble up whatever RAM you throw its way!
) and so one kernel ( do not tell me how much you have 
) is already serving the GUI…
Just like my Dual Silver Xeons, but I didn’t have THAT much money back then), so maybe I finally did something right this time. Interface is always locked - I don’t have any problems rendering the thing, just the long post loading process got me curious. And with my brain switched on, it seems somewhat logical 
