Kindle App crashes on MacBook Pro (with Mavericks)

Question

Hi Folks,
Every time I start my Kindle App in my MacBook Pro with network up it crashes after a few seconds. When network is down, it can work normally for several minutes, but sometimes it crashes too. Here what I got:
Dener macbook$ uname -a   <<-- my OS X version.
Darwin MacBook-Pro-de-Dener.local 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64
The Crash memory dump is:
Process:         Kindle [627]
Path:            /Applications/Kindle.app/Contents/MacOS/Kindle
Identifier:      com.amazon.Kindle
Version:         1.10.3 (1.10.40286)
App Item ID:     405399194
App External ID: 7062660
Code Type:       X86 (Native)
Parent Process:  launchd [176]
Responsible:     Kindle [627]
User ID:         501
Date/Time:       2014-04-16 16:50:10.336 -0300
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version:  11
Anonymous UUID:  C826805D-2207-7B7D-7B17-50C66872B8D8
Sleep/Wake UUID: 6573ECE7-93E4-4097-B98D-845B03085E7B
Crashed Thread:  0  Dispatch queue: com.apple.main-thread
Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
VM Regions Near 0x4:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/Kindle.app/Contents/MacOS/Kindle
    __TEXT                 0000000000001000-00000000014e4000 [ 20.9M] r-x/rwx SM=COW  /Applications/Kindle.app/Contents/MacOS/Kindle
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
and then comes a huge list of memory dump data....
appreciate any help!
dener

Answer 1

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.