Project hangs until I re-import whole project, over and over.

As to the arcanities of Pr's behavior ... way outside of my knowledge base! Might be just growing complexity or number of assets of the project, something else, dunno.

Of course, to modify a complex Project into a Production should be done with duplicated original project files. If you don't get it right, you can still work the original stand-alone project, right?

But though it could take a couple hours to create a Production, it might be worth it. As once you've created the Production (File/New Production), you make your folder setup to organize the project from the Production panel, and then you can create projects within subfolders and either import various assets into one or another project, or "Add Project", which brings a whole stand-alone project within that Production file.

And then you can grab assets from that project file, drop them into a different project within that production. This is discussed in that documentation ... and I'd read everything before starting.

@mattchristensen can be a big help with this. As can @Karl Soule'  ...

Ah, interesting! That could definitely make sense, I guess I can just make a secondary project with just the master files in it, I've just been going through the project with the director (who didn't make choices for takes before getting me to edit) and we have to go through all the original sequences, and then load them back into the main file. It's annoying but I guess it can make sense. 

Is there any reason why this would just start to happen in the last few weeks or so? I've been editing this project with equivalent size project files with all the same footage in it for the better part of 6 months. I'll take a look at those tutorials for sure. 

It sounds like you are working in a single, massive project file? For a feature length project? That ... is problematic.

Because Premiere must load all the metadata for the project into RAM/cache files, and with that large of a project, yea, that's slowing things down.

The Productions mode is what is recommended for episodic and feature projects. It's a vastly different methodology, and avoids the meta crunch issues.

In the Production mode, Premiere creates a series of folders on disc. Starting with the Production folder itself. You create subfolders within that main folder to organize your project, and within subfolders, projects to hold parts of the total job.

For instance, you may have a Media subfolder, with subfolders by day, location, or episode. Within each subfolder you have maybe a project with all the media, maybe several projects, each with only certain parts, like say, Red, Arri, Drone, and Stock projects.

In another folder off the main folder you might have Working Sequences and Master Sequences .... or maybe Editor Cuts, Director Cuts, Producer Cut ... however you're organized.

Within each folder are projects that have the sequences of those cuts. The media involved is simply gathered from the Media projects, and there is no duplication of assets within the Production.

Their actually best documentaion is about the Productions process, and the guide for "longform ... " linked below is actually one of the better docs on avoiding problems in Pr period. But then, Jarle Leirpoll was a main writer for this, so ... it's going to be worth reading for working pros.

Neil

Premiere Pro Productions Introduction

Using Productions in Premiere Pro

Adobe Long-form and Episodic Best Practices Guide 

Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multicam

I'm not even getting an error, it just goes to not responding, then if I wait ten minutes it starts to work, but really slowly, and then will hang (not responding) if I change something. But if I rebuild the project, it's fine. It's faster for me to make a new project and then re-import everything than opening up the same project. Then after a few hours it starts happening again. 😕😕 Annoying to say the least.

I have kind of the samie issue since adobe rolled out 24.0. i get the error code that there is not enough system space free for adobe to work properly. that never even occured before. i was wokring on a wedidng project. closed adobe. saw that there is a new update. did the update and now everything is broken. i also have the same issues as you that the project stops responding. completly freezes my whole system. my second monitor goes black and wont get recognized by windows unless i hard reset my computer. i never had any perfomance issues before this but now nothing is working ...