Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: DizzyDan35
DizzyDan35 Author
User level: Level 1
0 points

How can I stop Safari from crashing?

Hi

I tried updating software, erasing history/cache without success.

When I tried to send the full "report" on the crash, I couldn't post the question.

Suggestions?

This is a partial report.

Date/Time: 2015-05-20 19:44:11 -0400

OS Version: 10.10.3 (Build 14D136)

Architecture: x86_64

Report Version: 21


Command: Safari

Path: /Applications/Safari.app/Contents/MacOS/Safari

Version: 8.0.6 (10600.6.3)

Build Version: 1

Project Name: WebBrowser

Source Version: 7600006003000000

Parent: launchd [1]

PID: 6314


Event: hang

Duration: 1.80s (process was unresponsive for 38 seconds before sampling)

Steps: 19 (100ms sampling interval)


Hardware model: iMac11,2

Active cpus: 4


Fan speed: 999 rpm


--------------------------------------------------

Timeline format: stacks are sorted chronologically

Use -i and -heavy to re-report with count sorting

--------------------------------------------------


Heaviest stack for the main thread of the target process:

19 start + 1 (libdyld.dylib + 13769) [0x7fff939445c9]

19 NSApplicationMain + 1832 (AppKit + 13140) [0x7fff903d9354]

19 -[NSApplication run] + 594 (AppKit + 551923) [0x7fff9045cbf3]

19 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246 (Safari + 489840) [0x1070c8970]

19 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 (AppKit + 593768) [0x7fff90466f68]

19 _DPSNextEvent + 978 (AppKit + 596411) [0x7fff904679bb]

19 _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 205099) [0x7fff8a2ba12b]

19 ReceiveNextEventCommon + 431 (HIToolbox + 205546) [0x7fff8a2ba2ea]

19 RunCurrentEventLoopInMode + 235 (HIToolbox + 206191) [0x7fff8a2ba56f]

19 CFRunLoopRunSpecific + 296 (CoreFoundation + 465880) [0x7fff88675bd8]

19 __CFRunLoopRun + 927 (CoreFoundation + 467391) [0x7fff886761bf]

19 __CFRunLoopDoSources0 + 269 (CoreFoundation + 469901) [0x7fff88676b8d]

19 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 (CoreFoundation + 526849) [0x7fff88684a01]

19 ??? (<6D79CEE6-1F50-3534-A55D-9BB1934E3C55> + 4982178) [0x1083255a2]

19 ??? (<6D79CEE6-1F50-3534-A55D-9BB1934E3C55> + 4980439) [0x108324ed7]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 677684) [0x10858a734]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 669116) [0x1085885bc]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 2067692) [0x1086ddcec]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 980466) [0x1085d45f2]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 1651575) [0x108678377]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 75644) [0x1084f777c]

19 Safari::WK::iconDataReadyForPageURL(OpaqueWKIconDatabase const*, OpaqueWKURL const*, void const*) + 71 (Safari + 2444866) [0x1072a5e42]

19 Safari::SiteMetadataFetcherBundleClient::iconDataReadyForPageURL(Safari::WK::Ic onDatabase const&, Safari::WK::URL const&) + 212 (Safari + 3581058) [0x1073bb482]

19 Safari::SiteMetadataFetcher::faviconFetchFinished(NSData*, NSURL*, NSURL*) + 271 (Safari + 3572841) [0x1073b9469]

19 Safari::SiteMetadataFetcher::fetchCurrentRequest(Safari::SiteMetadataFetcher::R equestUserAgent) + 168 (Safari + 3570540) [0x1073b8b6c]

19 Safari::SiteMetadataFetcher::initOffscreenWebView(CGSize) + 196 (Safari + 3571850) [0x1073b908a]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 78729) [0x1084f8389]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 58656) [0x1084f3520]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 2334748) [0x10871f01c]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 1470204) [0x10864befc]

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 2063657) [0x1086dcd29]

19 ??? [0x7fc882703c50]

19 WebPageProxy_ctor_helper(void*, unsigned long long) + 115 (RapportDaishi.dylib + 33395) [0x10c245273]

19 web_page_monitor::create_monitor(void*, unsigned long long) + 203 (RapportDaishi.dylib + 55291) [0x10c24a7fb]

19 counted_ptr<web_page_monitor>::operator=(counted_ptr<web_page_monitor> const&) + 61 (RapportDaishi.dylib + 38883) [0x10c2467e3]

19 web_page_monitor::~web_page_monitor() + 92 (RapportDaishi.dylib + 52252) [0x10c249c1c]

19 generic_reader_writer_lock_base<grw_data_holder*, crisec_guard>::acquire_writer(bool) + 81 (trf.dylib + 214151) [0x10c6c6487]

19 semaphore_wait_trap + 10 (libsystem_kernel.dylib + 70938) [0x7fff9383a51a]

*19 semaphore_wait_continue + 0 (kernel + 1357760) [0xffffff800034b7c0]



Process: Safari [6314]

Path: /Applications/Safari.app/Contents/MacOS/Safari

Architecture: x86_64

Parent: launchd [1]

UID: 501

Task size: 61450 pages (+3)

CPU Time: 0.006s

Note: Unresponsive for 38 seconds before sampling

Note: 2 idle work queue threads omitted


Thread 0xd14ba DispatchQueue 1 19 samples (1-19) priority 46

<thread QoS user interactive, boosted, received importance donation from WindowServer [183], IO policy important>

19 start + 1 (libdyld.dylib + 13769) [0x7fff939445c9] 1-19

19 NSApplicationMain + 1832 (AppKit + 13140) [0x7fff903d9354] 1-19

19 -[NSApplication run] + 594 (AppKit + 551923) [0x7fff9045cbf3] 1-19

19 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246 (Safari + 489840) [0x1070c8970] 1-19

19 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 (AppKit + 593768) [0x7fff90466f68] 1-19

19 _DPSNextEvent + 978 (AppKit + 596411) [0x7fff904679bb] 1-19

19 _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 205099) [0x7fff8a2ba12b] 1-19

19 ReceiveNextEventCommon + 431 (HIToolbox + 205546) [0x7fff8a2ba2ea] 1-19

19 RunCurrentEventLoopInMode + 235 (HIToolbox + 206191) [0x7fff8a2ba56f] 1-19

19 CFRunLoopRunSpecific + 296 (CoreFoundation + 465880) [0x7fff88675bd8] 1-19

19 __CFRunLoopRun + 927 (CoreFoundation + 467391) [0x7fff886761bf] 1-19

19 __CFRunLoopDoSources0 + 269 (CoreFoundation + 469901) [0x7fff88676b8d] 1-19

19 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 (CoreFoundation + 526849) [0x7fff88684a01] 1-19

19 ??? (<6D79CEE6-1F50-3534-A55D-9BB1934E3C55> + 4982178) [0x1083255a2] 1-19

19 ??? (<6D79CEE6-1F50-3534-A55D-9BB1934E3C55> + 4980439) [0x108324ed7] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 677684) [0x10858a734] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 669116) [0x1085885bc] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 2067692) [0x1086ddcec] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 980466) [0x1085d45f2] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 1651575) [0x108678377] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 75644) [0x1084f777c] 1-19

19 Safari::WK::iconDataReadyForPageURL(OpaqueWKIconDatabase const*, OpaqueWKURL const*, void const*) + 71 (Safari + 2444866) [0x1072a5e42] 1-19

19 Safari::SiteMetadataFetcherBundleClient::iconDataReadyForPageURL(Safari::WK::Ic onDatabase const&, Safari::WK::URL const&) + 212 (Safari + 3581058) [0x1073bb482] 1-19

19 Safari::SiteMetadataFetcher::faviconFetchFinished(NSData*, NSURL*, NSURL*) + 271 (Safari + 3572841) [0x1073b9469] 1-19

19 Safari::SiteMetadataFetcher::fetchCurrentRequest(Safari::SiteMetadataFetcher::R equestUserAgent) + 168 (Safari + 3570540) [0x1073b8b6c] 1-19

19 Safari::SiteMetadataFetcher::initOffscreenWebView(CGSize) + 196 (Safari + 3571850) [0x1073b908a] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 78729) [0x1084f8389] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 58656) [0x1084f3520] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 2334748) [0x10871f01c] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> + 1470204) [0x10864befc] 1-19

19 ??? (<DFBBC814-0A22-3361-B93D-2C40B86FD238> +



Thanks

iMac, Mac OS X (10.6.6)

Posted on May 20, 2015 4:56 PM

Reply
Question marked as Best reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Posted on May 20, 2015 7:45 PM

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

View in context
6 replies
Question marked as Best reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

May 20, 2015 7:45 PM in response to DizzyDan35

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Reply
User profile for user: DizzyDan35
DizzyDan35 Author
User level: Level 1
0 points

May 23, 2015 9:01 AM in response to Linc Davis

Here is the information as requested.


LOG LIST REPORT:


5/23/15 10:47:56.683 AM com.apple.usbmuxd[83]: ClientSendDictionary to client 0x100615b00-Safari/com.apple.Safari failed to send flat data: -1, Resource temporarily unavailable



THERE WERE TWO DIAGNOSTIC REPORTS, THE FIRST WAS RELATED TO THE WEBKIT THE SECOND TO SAFARI


#1

Responsible: Safari [37189]

0x7fff913a8000 - 0x7fff91d05fff com.apple.Safari.framework (10600 - 10600.5.17) <83AB27C4-CD1B-31FB-91C3-23E9CEC124F9> /System/Library/PrivateFrameworks/Safari.framework/Versions/A/Safari


#2

Process: Safari [12379]

Path: /Applications/Safari.app/Contents/MacOS/Safari

Identifier: com.apple.Safari

Responsible: Safari [12379]

com.SiberSystems.rf-safari-924KXEUXP3 (2.1.1 - 2.1.1) RoboForm

6 com.apple.Safari.framework 0x00007fff9176fec3 -[UnifiedField layout] + 108

9 com.apple.Safari.framework 0x00007fff91777f3f -[UnifiedField _animateToResignFirstResponder] + 542

21 com.apple.Safari.framework 0x00007fff9141f970 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

Thread 19:: Safari: WBSParsecSearchClient location

5 com.apple.Safari.framework 0x00007fff919aad6e -[WBSParsecSearchClient _locationThread] + 43

Thread 20:: Safari: SafeBrowsingManager

5 com.apple.Safari.framework 0x00007fff91626427 Safari::MessageRunLoop::threadBody() + 147

6 com.apple.Safari.framework 0x00007fff916265c5 void* std::__1::__thread_proxy<std::__1::tuple<Safari::MessageRunLoop::createThreadIf Needed()::$_0> >(void*) + 90

0x102d46000 - 0x102d46fff com.apple.Safari (8.0.5 - 10600.5.17) <E87842F8-F207-3F85-BA62-644CCE273825> /Applications/Safari.app/Contents/MacOS/Safari

0x10b4c0000 - 0x10b4cdfff +com.evernote.EvernoteSafariClipperPlugin (1.0 - 195746) <A2D10139-2F6B-3F21-8509-0B0C80CF1D39> /Users/USER/Library/Internet Plug-Ins/EvernoteSafariClipperPlugin.webplugin/Contents/MacOS/EvernoteSafariCli pperPlugin

0x10b4e0000 - 0x10bb91fef +Siber-Systems.rf-safari-plugin (2.1.1 - 2.1.1) <56DDA90D-A382-335E-BD69-20FE89BD6598> /Users/USER/Library/Internet Plug-Ins/rf-safari-plugin.webplugin/Contents/MacOS/rf-safari-plugin

0x7fff913a8000 - 0x7fff91d05fff com.apple.Safari.framework (10600 - 10600.5.17) <83AB27C4-CD1B-31FB-91C3-23E9CEC124F9> /System/Library/PrivateFrameworks/Safari.framework/Versions/A/Safari

0x7fff96d87000 - 0x7fff96d89ff3 com.apple.SafariServices.framework (10600 - 10600.5.17) <55E7D2A9-802C-36E9-9D38-A2D34107740D> /System/Library/PrivateFrameworks/SafariServices.framework/Versions/A/SafariSer vices

0x7fff99039000 - 0x7fff99039fff com.apple.SafariDAVNotifier (1.1.1 - 1) <21D4673A-52C7-391D-AF7C-F77D368D34AE> /System/Library/PrivateFrameworks/BookmarkDAV.framework/Versions/A/Frameworks/S afariDAVNotifier.framework/Versions/A/SafariDAVNotifier



Thanks!

dan

Reply
User profile for user: DizzyDan35
DizzyDan35 Author
User level: Level 1
0 points

May 25, 2015 8:02 AM in response to Linc Davis

Thanks.

You have been generous with your time.

I will need to contact Trusteer. When I searched for the program. rapport.dmg, there was none in searchlight. Then I went to Finder and found the uninstall icon, but when i clicked on it it said, "uninstall rapport is damaged and can't be opened. You should eject the disk image." So that didn't work. Next I went to the "Console" and updated rapport. I will see if it keeps crashing.

I will update after I get through this or find it stops crashing.

My bank recommended I install Rapport.

Thanks again,

In memorial for those who have given the ultimate, I wish you well.

Dan

Reply

How can I stop Safari from crashing?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up