The macosxhints Forums

The macosxhints Forums (http://hintsforums.macworld.com/index.php)
-   Applications (http://hintsforums.macworld.com/forumdisplay.php?f=5)
-   -   Addressbook (constantly) unexpectedly quits... (http://hintsforums.macworld.com/showthread.php?t=13177)

learner 07-05-2003 08:26 PM

AKcrab,

I do the fsck -y in single user mode, and the repair permission several times a day...

thks...:)

djn1 07-05-2003 08:39 PM

Quote:

Originally posted by learner
Strange all the aliases...

Hope you cope...:D
The aliases are normal and the content looks normal too.

What puzzles me, however, is the code you posted:
Code:

2003-07-06 01:24:15.452 Safari[980] ABAddressBook could not aquireLock:
writeLock error No such file or directory: 'Framework/AddressBook/ABAddressBook.m' line: 1396
2003-07-06 01:24:15.453 Safari[980] -[ABAddressBook _initDefaultContactManager]
Can't _acquireLock Framework/AddressBook/ABAddressBook.m:1403
Jul  6 01:24:15 xxx's-Computer /Applications/Safari.app/Contents/MacOS/Safari:
An error report file has been saved as /Users/xxx/Library/Logs/JavaNativeCrash_pid980.log. 
Please refer to the file for further information.

Does anyone know what "Framework/AddressBook/ABAddressBook.m" refers to? I can't find this anywhere on my system (using either Finder or Locate).

yellow 07-05-2003 10:55 PM

Quote:

Originally posted by learner
I do the fsck -y in single user mode, and the repair permission several times a day...
Several times a day? Don't waste your time. There's no real need to do this until after an Apple update via Software Updater or the old fashioned way (via self download & install).

learner 07-06-2003 08:39 AM

yellow,

I understand that.
But at this time it is part of my constant troubleshooting proces.

thks :)

djn1 07-06-2003 09:16 AM

Have you tried creating another (admin) user account to see whether the problem is system wide rather than related to something in your normal user account?

learner 07-08-2003 07:37 AM

djn1

Sorry, I didnot respond right away, but I am working abroad now and the access to the internet is not always possible. :eek:

I created another account as you suggested and whoops... The addressbook opened without any difficulties. :p:p:p

Great.. Never thought about that... Gives me hope again... See if things change in course of time...

thks:)

Sumleilmus 08-02-2003 04:45 PM

New User worked, but didn't fix Safari crash-o-rama
 
I've been vexed by the Safari and AddressBook crashes at launch on 2 different machines: an older 267 G3 and a newer 700 G4.

Creating a new admin user enabled Safari and Address Book not to crash, but when I logged in as other users, the problem was Still There.

I've read this entire thread, and tried everything here . . . except the full reinstall.

I found this suggestion elsewhere on the web, and fixing the permissions for Application Support for one user solved the problem for all.

(I found this solution by feeding snips of the crashlog entry into Google.)

*********
the following Crashlog entry:

2003-08-01 14:01:56.692 Mail[593] ABAddressBook could not aquireLock:
writeLock error No such file or directory:
'Framework/AddressBook/ABAddressBook.m' line: 1396
2003-08-01 14:01:56.692 Mail[593] -[ABAddressBook
_initDefaultContactManager] Can't _acquireLock
Framework/AddressBook/ABAddressBook.m:1403

It seems Safari requires Address Book. I've looked at the Knowledge Base with no success. Reinstall 10.2 from CD, zap PRAM, drag working copies of Mail and Address Book, with their plists on the Dual, used TechTool 3.09, Drive 10, Norton SystemWorks for X, and no fix.

I experienced the same problem with Address Book, Mail, iCal, and any other program that references the OS-X address book. It turned out to be a privilege/ownership problem in which, somehow, a directory under my /Users/username/Library had been changed to have "root" ownership.

The following commands from the terminal window fixed the problem for me:

cd /Users/username/Library
sudo chown username:group "Application Support"
cd "Application Support"
sudo chown username:group AddressBook
*************

You are a bunch of Pretty Smart Guys, so I probably missed the part higher in this thread about checking permissions, but, I must say, finding this tip solved all my problems. (I think the original post was by Jeffrey Paduan.)

petey 08-02-2003 06:11 PM

Quote:

Originally posted by djn1

I agree that APE can cause problems but I think you might be jumping the gun in this instance.
because APE loads into every application's space, any crash log will refererence APE whether it was responsible for the crash or not.

i use APE with no noticeable problems, but acknowledge it certainly can create problems.

and mervTormel: why do you have APE references if you don't have APE installed? am i missing something?

mervTormel 08-02-2003 06:34 PM

Quote:

Originally posted by petey
...and mervTormel: why do you have APE references if you don't have APE installed? am i missing something?
hmm, coulda sworn i had a vanilla install with __ape refs in a crash log. now, can't find it.

so, i thought that __ape isn't necessarily unsanity's APE.

djn1 08-03-2003 10:27 AM

Quote:

Originally posted by mervTormel
hmm, coulda sworn i had a vanilla install with __ape refs in a crash log. now, can't find it.

so, i thought that __ape isn't necessarily unsanity's APE.
This might clarify issues slightly (taken from Unsatity's website):

Code:

Why is APE causing my computer to crash?
                       

It isn't. If an APE is causing a crash (APE itself will not), then in
the crash log you will see "APEBundleMain" or "APEBundleMessage"
in the crash log and right above the section with "APEBundleMessage"
it will say "Thread N Crashed:". Only then would it have been caused
by an APE module (but not by APE itself).
 
 Example of an APE module crashing (was done on purpose to show an example):
 
 Thread 0 Crashed:
  #0  0x9068ba54 in objc_msgSend
  #1  0x90131f64 in CFRelease
  #2  0x004604ec in APEBundleMessage
  #3  0x004602e8 in APEBundleMessage
 
 If you see
 
 Thread 2:
  #0  0x90073c28 in mach_msg_trap
  #1  0x90005f70 in mach_msg
  #2  0x00463ac4 in APEBundleMessage
  #3  0x90020d28 in _pthread_body
 
 or:
 
 Thread 1:
  #0  0x90073c28 in mach_msg_trap
  #1  0x90005f70 in mach_msg
  #2  0xc0007758 in __ape_internal
  #3  0xc0001160 in __ape_agent
  #4  0x90020d28 in _pthread_body
 
this does not mean that APE caused the crash or had anything to do
with a crash. This is a thread (concurrently running instructions) that
just listens for messages from the different preference panes that
control APE Modules like APE Manager. Otherwise it just sits there idling
and uses no CPU.



All times are GMT -5. The time now is 03:23 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Site design © IDG Consumer & SMB; individuals retain copyright of their postings
but consent to the possible use of their material in other areas of IDG Consumer & SMB.