Comments on: Flock crashing on G5

By: Chris Messina

Chris Messina — Mon, 05 Dec 2005 07:25:56 +0000

Well, I’ve filed a bug on this issue! Thanks for pointing it out.

By: Mark

Mark — Fri, 02 Dec 2005 19:35:31 +0000

Well to be honest that was going to be the next step. Deleting a plist file is a bit less invasive than trashing an entire folder.

The step after that involved you reformatting the boot volume, reinstalling Tiger, and promising to never use Flock again. ;-P (I learned that trick from customer support for Windows)

By: Tom Raftery

Tom Raftery — Fri, 02 Dec 2005 19:13:24 +0000

I forgot to say Mark, I deleted the .plist file first - no joy, but deleting the Application Support/Flock folder worked a treat!

By: Mark

Mark — Fri, 02 Dec 2005 19:12:42 +0000

Excellent.

By: Tom Raftery

Tom Raftery — Fri, 02 Dec 2005 18:45:39 +0000

Mark,

I deleted the Library/Application Support/Flock folder and that sorted the problem.

By: Mark

Mark — Fri, 02 Dec 2005 18:17:46 +0000

Oh yeah, garbage plist files in, crashing applications out.

As I learned when Windows Media Player for Macintosh started crashing out after I migrated to my PowerMac G5 and then upgraded to 10.4, some applications don’t clean up after themselves. You might have dumped the app but it’s preference file could still be hanging around in a Library folder. A corrupted plist can cause apps to crash out on launch as some preference files are only generated if it can’t find one to begin with.

http://homepage.mac.com/jonn8/as/html/pt.html

If this solves your problem let me know.

By: Tom Raftery

Tom Raftery — Fri, 02 Dec 2005 18:10:36 +0000

Mark,

yeah, there’s loads written there - even more written to /Library/Logs/CrashReporter/flock-bin.crash.log

Nothing I could make much sense of though - for instance:

Thread 5 Crashed:
0 libxpcomclucene.dylib 0×0360c9c4 NSGetModule + 5280
1 libxpcomclucene.dylib 0×0360d52c NSGetModule + 8200
2 libxpcomclucene.dylib 0×03608b20 dyld_stub__ZSt8_DestroyIPPN6lucene5index4TermESaIS3_EEvT_S6_T0_ + 56413888

By: Mark

Mark — Fri, 02 Dec 2005 17:58:39 +0000

Anything written to the console.log? You can monitor it in realtime by tailing the file in a Terminal or just opening Console.app in the Utilities folder.

By: Tom Raftery

Tom Raftery — Fri, 02 Dec 2005 17:12:01 +0000

That could well be it Gary but I don’t think so - it hapened with the older version of Flock which was on my PowerBook, when I copied it across and the newer version when I installed it.

Also, it doesn’t exhibit the reported behaviour of this bug - it doesn’t even allow Flock to launch - it crashes almost immediately after launching - no page is ever displayed!

By: gpshewan

gpshewan — Fri, 02 Dec 2005 17:05:43 +0000

Could it be because of the Firefox issues on G5 chips? Flock would be a lot more intensive and is built on FF

http://businesslogs.com/technology/crippling_firefox_bug_on_mac_os_x.php