Google Chrome crashes when downloading a file

Question

recently my google chrome crashes every time I try to download a file with it, I have attached the console output after looking at it several times and not being able to figure out the issue exactly. I appreciate your assistance:
Process:         Google Chrome [169]
Path:            /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:      com.google.Chrome
Version:         30.0.1599.101 (1599.101)
Code Type:       X86 (Native)
Parent Process:  launchd [134]
User ID:         501
Date/Time:       2013-10-20 23:36:09.196 +0400
OS Version:      Mac OS X 10.8.5 (12F45)
Report Version:  10
Crashed Thread:  0  CrBrowserMain  Dispatch queue: com.apple.main-thread
Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   com.google.Chrome.framework             0x008c0f27 0xb3000 + 8445735
1   com.google.Chrome.framework             0x008dc89f 0xb3000 + 8558751
2   com.google.Chrome.framework             0x002329f2 0xb3000 + 1571314
3   com.apple.CoreFoundation                0x946186e9 +[NSException exceptionWithName:reason:userInfo:] + 73
4   com.apple.AppKit                        0x96cb5b54 -[NSBrowser setSelectionIndexPaths:] + 1019
5   com.apple.AppKit                        0x96cb52d0 -[NSBrowser setSelectionIndexPath:] + 87
6   com.apple.FinderKit                     0x958d0975 -[FI_TColumnViewController openTarget] + 1214
7   com.apple.FinderKit                     0x95915d2d -[FIFinderViewGutsController commonFinishInitialization] + 119
8   com.apple.FinderKit                     0x9590f04a -[FIFinderViewGutsController createBrowserViewWithViewStyle:] + 590
9   com.apple.FinderKit                     0x9591139c -[FIFinderViewGutsController buildBrowserView:] + 224
10  com.apple.FinderKit                     0x959118cf -[FIFinderViewGutsController _internalSetTargetPath:withViewStyle:] + 695
11  com.apple.FinderKit                     0x95911afa -[FIFinderViewGutsController setTargetPath:withViewStyle:] + 47
12  com.apple.FinderKit                     0x95910ce8 -[FIFinderViewGutsController setTargetNode:withViewStyle:] + 573
13  com.apple.FinderKit                     0x9591092a -[FIFinderViewGutsController setTargetNode:] + 64
14  com.apple.FinderKit                     0x95912643 -[FIFinderViewGutsController deferredRetargetAndReloadForNode:] + 383
15  com.apple.FinderKit                     0x95912a1e -[FIFinderViewGutsController urlResolutionCompleted:] + 163
16  com.apple.Foundation                    0x92c49e52 __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_0 + 49
17  com.apple.CoreFoundation                0x9467a851 ___CFXNotificationPost_block_invoke_0 + 257
18  com.apple.CoreFoundation                0x945c5e8a _CFXNotificationPost + 2794
19  com.apple.Foundation                    0x92c32988 -[NSNotificationCenter postNotificationName:object:userInfo:] + 92
20  com.apple.Foundation                    0x92c42727 -[NSNotificationCenter postNotificationName:object:] + 55
21  com.apple.FinderKit                     0x9590c409 -[FI_FinderURLResolver resolutionCompleted:] + 99
22  libobjc.A.dylib                         0x990895d3 -[NSObject performSelector:withObject:] + 70
23  com.apple.Foundation                    0x92c81326 __NSThreadPerformPerform + 395
24  com.apple.CoreFoundation                0x9458f04f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
25  com.apple.CoreFoundation                0x9458eb49 __CFRunLoopDoSources0 + 441
26  com.apple.CoreFoundation                0x945b4826 __CFRunLoopRun + 934
27  com.apple.CoreFoundation                0x945b401a CFRunLoopRunSpecific + 378
28  com.apple.CoreFoundation                0x945b3e8b CFRunLoopRunInMode + 123
29  com.apple.HIToolbox                     0x9a0fef5a RunCurrentEventLoopInMode + 242
30  com.apple.HIToolbox                     0x9a0febf5 ReceiveNextEventCommon + 162
31  com.apple.HIToolbox                     0x9a0feb44 BlockUntilNextEventMatchingListInMode + 88
32  com.apple.AppKit                        0x96a3293a _DPSNextEvent + 724
33  com.apple.AppKit                        0x96a3216c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
34  com.apple.AppKit                        0x96a285cc -[NSApplication run] + 855
35  com.google.Chrome.framework             0x008ac74b 0xb3000 + 8361803
36  com.google.Chrome.framework             0x008ac27c 0xb3000 + 8360572
37  com.google.Chrome.framework             0x008e4501 0xb3000 + 8590593
38  com.google.Chrome.framework             0x008fa1b1 0xb3000 + 8679857
39  com.google.Chrome.framework             0x00239e8b 0xb3000 + 1601163
40  com.google.Chrome.framework             0x02c7a610 0xb3000 + 45905424
41  com.google.Chrome.framework             0x02c7b193 0xb3000 + 45908371
42  com.google.Chrome.framework             0x02c76bde 0xb3000 + 45890526
43  com.google.Chrome.framework             0x00805e95 0xb3000 + 7679637
44  com.google.Chrome.framework             0x00805220 0xb3000 + 7676448
45  com.google.Chrome.framework             0x000b5a39 ChromeMain + 41
46  com.google.Chrome                       0x000aef78 main + 24
47  com.google.Chrome                       0x000aef55 0xae000 + 3925

Answer 1

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not  going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.