Hanging when updating Libraries from older versions #305
Comments
latenitefilms
changed the title
|
@stevef243 - Apple says:
I will send them your previous log files. |
|
lol that’s Apple the system log obviously was from the computer I had the issue with. Now on Holliday so out for two weeks
…On 16 Dec 2023 at 14:36 +1100, Chris Hocking ***@***.***>, wrote:
@stevef243 - Apple says:
> The sysdiagnose you provided did not show any hangs or spins pertaining to FCP. Can you please attach a sysdiagnose from the computer that had the issue?
I will send them your previous log files.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
It's possible I could have accidentally included my system logs - as the Feedback Assistant Mac app will automatically grab all your log files - although I did link to this GitHub issue and your Google Drive link in the feedback. |
|
I can’t check now but pretty sure I provided correct file and certainly created log on my work machine as that’s the only one I’m using for FCP
…On 16 Dec 2023 at 16:21 +1100, Chris Hocking ***@***.***>, wrote:
It's possible I could have accidentally included my system logs - as the Feedback Assistant Mac app will automatically grab all your log files - although I did link to this GitHub issue and your Google Drive link in the feedback.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
This seems to have been fixed in 10.7.1 just updated many libraries without hangs |
|
actually still does happen especially with bigger libraries |
|
and again need to force quite FCP |
|
strange did 20 Liabraries no issue and now FCP hangs on each Library Date/Time: 2023-12-28 12:02:28.644 +1100 Data Source: Stackshots Command: Final Cut Pro Event: hang Hardware model: Mac13,1 Time Since Boot: 18608s Fan speed: 1382 rpm Processes reached dispatch thread soft limit (64): Final Cut Pro [17478] Preferred User Language: en-AU, de-AU Timeline format: stacks are sorted chronologically
|
|
This one even gave me FCP Crash window https://drive.google.com/file/d/1Ox0Iz8TDvwsRoyl_XSLQ2qc6pCUY36GJ/view?usp=sharing |
|
When re-opening FCP, the Libraries, which seemed to have stuck and crashed FCP, are updated and seem to work. |
|
@stevef243 - Apple has sent me this:
|
|
have finally all Libraries updated with quite a few crashes so at the moment could not reproduce |
|
Do you have those crash logs you can share? Do you want me to close this issue? |
|
These crash logs should be from the updates |
|
Do you have backups of the libraries before updating, so that you can reproduce the hang? I don't think Apple will be able to do much more without a hang log or sample of the FCP whilst hanging. |
|
no, I update the backup also. What exactly is a hanging log? And what sample while it's hanging, just for further reference? |
|
Hanging is when you force quit the app, rather than it crashing by itself. Hanging logs end up in the same place as crash logs. You can Sample a process using Activity Monitor: 
It basically just creates log files of everything Final Cut Pro was doing at the time of the sample. |
|
Strange, I have all crash logs from that time 1st Jan , but there is not a single hanging log in the same location |
|
Try looking at the Finder Level? |
|
Hangs might also be in the "Spin Reports" section? I'm not actually sure what Spin Reports refers to, as the documentation is unclear: https://support.apple.com/en-au/guide/console/cnsl664be99a/mac |
|
yes checked that it's empty |
Apple Feedback Assistant ID: FB13464670
DESCRIBE THE BUG:
FCP is hanging when loading Data Bases, which need updating. Noticed this now quite a few times
TO REPRODUCE:
cant always reproduce but several times FCP hang after updating the DB. Once you Force Quite FCP and restart the DB seems to behave normally
EXPECTED BEHAVIOUR:
FCP not hanging when updating a DB
SCREENSHOTS:
SPECS:
ADDITIONAL COMMENTS:
no crash logs again in folder
Apps Diagnostic link
https://drive.google.com/file/d/1l3_84ylJObzp30LH_B_vJyU8iaobVxTv/view?usp=sharing
The text was updated successfully, but these errors were encountered: