Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10.6.7 Random Beach Balls After Working A While #230

Open
Unboundclassic opened this issue Jul 26, 2023 · 1 comment
Open

10.6.7 Random Beach Balls After Working A While #230

Unboundclassic opened this issue Jul 26, 2023 · 1 comment

Comments

@Unboundclassic
Copy link

Unboundclassic commented Jul 26, 2023

Apple Feedback Assistant ID: FB12759754

Describe the bug
I think I've see others mentioning this 10.6.7 bug. But I'll add it to the pile... In general I haven't had issues with 10.6.7 - except that after a random amount of time I do an action (doesn't seem to be consistent) and I get a super long beach ball. After that any action starts another beach ball. So I have to quit FCP, which takes longer than normal. After restarting FCP everything is back to normal... for a while till it does it again. Definitely annoying. It's happened across a number of different Libraries.

To Reproduce
Steps to reproduce the behavior:

  1. Open a Library
  2. Start working
  3. Work for a while
  4. Beach balls start

Screenshot 2023-07-26 at 1 41 43 PM

Expected behavior
Working without project stopping beach balls.

Desktop (please complete the following information):

  • OS: Ventura 13.4.1 ©
  • Browser Safari
  • Version 16.5.2

Additional context
Add any other context about the problem here.

@joema4
Copy link

joema4 commented Jul 29, 2023

When it's in that state, I recommend taking a spindump and posting that file here. Chris or I can look at it and in some cases we can deduce something. If not, at least a record of those may help assemble a pattern that later proves useful. To take a spindump, run Activity Monitor, select the non-responding FCP process (it will usually be in red text), do View>Run Spindump. When it's finished, in the upper-right corner click "Save". Typical size: about 7MB, if ZIP'd, about 500KB.
Make sure it's in the hung or beachball state when the spindump is taken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants