The bug here makes me nervous for the weekend, as I know I would subconsciously "Clone" things at times, and risk crashing C3 (I checked and also get crash):
github.com/Scirra/Construct-bugs/issues/8338
Before I knew of this bug, I had already moved to the beta and continued working, made a lot of progress (and have earlier backup of old version, for worst case).
I however don't want to risk the crash occurring, so I "edited project file, reverted back to r416". Spent few mins testing, seemed fine, made 2 or 3 changes including animation rename, 2 new events, hit "Save", and the save locked-up on "Working...". I waited a while, no difference. Closed and reopened C3 still in r416, but turns out my project corrupted and cannot be opened (but of course I have backups, phew!)
I tested again (got my r417 backup, downgraded again, made different changes), but thankfully did not have same save issue and project did not corrupt. Checked HDD space, all healthy. Never had issues with save like this before. Unsure why/what happened, may not relate to downgrading, but as mentioned, never had such save issues ever, in years of using C3. (Chrome, no extensions, no VPN, no new things on PC, can save fine in both versions still).
I think I will stick to r417 in this case as the risk is much less and I rather not use old backup and redo work I have recently done, but I would be eternally grateful to see a hotfix for this "Clone" crash, before the weekend commences, if possible at all?
I wouldn't usually ask, but just on the case of "Clone" being common and ingrained in my workflow, and feeling too risky to backport and corrupt my project (whether this was a rare unrelated save issue or not, I am not sure, but if related, definitely do not want other eager beta users making same mistake as me).
The red crash screen certainly sends a shock of "OH NO" down my spine, so anything to avoid this is greatly appreciated - Having Diego recently solve the "bookmark bar" crash has been ethereal to be able to use bookmarks without risking a red crash screen! I suppose I could be testing the r417 crash screen when cloning, maybe the "Save project" button works fine (although it makes me nervous since, what IS it saving in the red crash screen, the cloned broken object? Maybe it's ok, maybe not).
I hold my hands up that I could have tested more correctly before moving to beta, and it's not on Scirra to fix my own choices, but wanted to try asking just in case it is feasible.
I always use beta, always have backups, haven't lost work ever (or never a significant amount)!
EDIT: I tested r417, cloned, crash, "Save projects" from crash screen, opened, and seems fine, doesn't include the cloned object, but of course not sure what damage might occur. The downside though, is, I use "Folder Save", and measuring time to "Save project from crash, open c3p file, save as project folder again" takes about 2 to 3 minutes to do. I do not look forward to encountering this bug many times over the weekend, piling up to be many minutes of time lost, along with nervousness if the recovered c3p file is broken in any way.