304876 - Camino is hanging after period of inactivity and continues to hang intermittently after initial recovery ([KindaSmartFolderManager availableServicesChanged:])

Status: VERIFIED WORKSFORME

(Camino Graveyard :: General, defect)

Description

[David Poole]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050731 Camino/0.9a2+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050731 Camino/0.9a2+

The hangs on seem to happen if I leave the browser alone and come back to it. 
It eventually recovers, but will start to hang frequently during use to the
point where the application has to be killed.

This only seems to happen on one of my machines, PowerMac Dual G4.  It has never
been an issue on my Powerbook.  Both machines are using same Camino build and OS
version.  

Reproducible: Always

Steps to Reproduce:
1. Browse as one normally would
2. Hide or don't use Camino for an extended period of time.
3. Come back and it hangs.

Actual Results:  
It hangs than eventually recovers.  Once it recovers it starts to hang more
frequently until the app freezes all together and has to be killed.

Comment 1

[David Poole]

Attachment: An example from Spin Control

Comment 2

[David Poole]

Attachment: A stack trace from a long hang

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Are you on 10.3.x or 10.4.x?

Comment 4

[David Poole]

Currently 10.4.2, but I have experienced this issue with 10.3.

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Thought it might have been bug 297343, which I believe is 10.4-only, but maybe
it's bug 301513 or bug 301404.

There's a definite up-tick in the number of random beachballing bugs (also bug
301745, and bug 303380 on the 1.7 branch, off the top of my head).  Simon, Mike,
do any of these seem like dupes?

Comment 6

[Simon Fraser [no longer active]]

The second stack trace has a lot of samples under
-[KindaSmartFolderManager availableServicesChanged:]

Comment 7

[David Poole]

With 1.0a1 I am no longer experiencing this.

Comment 8

[Simon Fraser [no longer active]]

Please reopen if you see the problem again.