Thanks for the details!  Are you perhaps using any 3rd party plugins or extensions, in PPro? [Not pointing fingers, just looking for info...]   ... View more

Yours is the first report of anything like this behavior. If you can provide steps which reliably reproduce the behavior, we'd be happy to pursue it further.  It would be interesting to know whether projects NOT in iCloud-sync'd folders display anything like this behavior, on your system.  ... View more

On what sort of storage, does your Production live; local disk? NAS?  ... View more

>Is there a temporary/cache location where autosave projects are stored? Only the scratch disk location, in your Production settings. ... View more

Looking... ... View more

>That should be very helpful to Adobe to get rid of this bug. We wish! Actually, it isn't.  We're urgently investigating this issue, and it would very much help us to know (from any of you who've encountered it); what sort of tasks were you doing in PPro, around the time your project(s) first became corrupted? [We realize you likely didn't discover the problem immediately, but even general guidance like "messing with the transcript" or "fiddling with effects parameters" might provide useful clues...] ... View more

Also...what does that dialog box, actually say? ... View more

We can make absolutely no promises, and...I've DM'd you my email address, so you can send us the project.  [Do you have any auto-saves that DO open? If so, send those too] ... View more

I got the .prproj and an .mp4 file, thanks! Nothing I've tried has caused any problems, on Mac or Win, in official or beta PPro builds.  What steps can I follow, to see what you're seeing? ... View more

If what you've provided repros the issue, we're all set!  ... View more

I DM'd you the link.  Ideal = A project containing that sequence and its constituent media, as well as steps we can follow which reliably cause PPro to eat all system memory. ... View more

More good clues! Do you have a piece of media which, when added to a sequence, reliably makes PPro eat all available memory? If so...can we have it? [I can provide private upload space, if desired.] ... View more

Good details, thanks! The amount of disk storage necessary to hold PPro, (that 5gb number) is completely unrelated to the amount of RAM used by PPro (that 108gb number).  What were you doing in PPro, right before the force-quit dialog appeared? Does PPro use all your memory, every time you run it, or only when performing certain tasks? ... View more

Hi Zoe, The size of a project file on disk, is distinct from the amount of RAM needed to load that project into memory.  What did the pop up you saw, say?  What memory usage setting are you currently using?  Have you always encountered problems like this, on this editing system? If not...what changed about your system? ... View more

No, we have no plans to expose or document the information in object mask files.  As mentioned elsewhere, we'd be happy to help with "plugin stopped working", provided some actionable specifics...? ... View more

If the user triggers Undo, your effect does receive the previous parameters (with correct state info), right?  >Plug-ins should receive a PF_Cmd_USER_CHANGED_PARAM command regardless of how a parameter value has changed... A distinction, which may or may not make a difference: In the case you describe, the user doesn't change the param; they instead invoke Undo, to avoid changing the param.  In that case, where Undo obviates any changes to the param, I'm struggling to understand the cases where your plugin would want any outcome, other than the one provided by the host given your plugin the previous, valid params.  This doesn't (yet) make sense to me:  PPro: "Okay, the user said they didn't want any changes, so I put everything back where it was...but here's a PF_Cmd_USER_CHANGED_PARAM message, just in case!"  ... View more

Hi FxFactory & OMotion, We believe you, and...Can either of you provide a plugin, that reproduces the behavior described?  When you say 'slider' params, do you mean PF_Param_FIX_SLIDERs as well as PF_Param_FLOAT_SLIDERs? ... View more

Although I was never able to reproduce problems exporting AAF, I'm told that, yes, the fix we've tested applies AAF as well (which also displays multiple dialogs, during export). ... View more

>...might just be accessible by ExtendScript You're welcome to try, but we're not optimistic about your chances for success. Our recommendation remains waiting for UXP extensibilitys support; no dates available. ... View more

Strange!  Where do you set the in/out points for the sequence; in the Program Monitor, Timeline, or Source Monitor?  You say the problem began ~3 weeks ago; did you change PPro versions around that time, or were you using 25.4.0x99 before and after the strange behavior began? ... View more

Update: Yep, you've identified a legitimate bug, introduced in recent beta builds. Fix forthcoming!  ... View more

We're tried, but cannot reproduce the freeze, based on the information you've provided.  Confirming: in PPro beta builds (currently version 26.x), you can reproduce the freeze 100% of the time, exporting 100% of the sequences you've tried?  ... View more

Bizarre. Are you on Windows?  If you specify a different (completely arbitrary) destination directory, then successfully export, then try to export a sequence from within a Production project, does the Production name once again get prepended? ... View more