safari crash when dragging any image/text (A problem occurred with this page so it was reloaded.)

Question

Level 1

16 points

safari crash when dragging any image/text (A problem occurred with this page so it was reloaded.)

Hi Gang,

seems that after upgrading to Safari 10.1 (11603.1.30.0.34) each time I try to click and drag an image (or highlight some text/link and then DRAG) ... immediately Safari crash and present message "A problem occurred with this webpage so it was reloaded.", then Safari reload the page and crash report pop-up.

Already tried all the "known" tricks (plist, guest user, etc) none worked.

Please see some info pasted below. Any ideas?

Thanks for your help.

~mark [😠]

Process: com.apple.WebKit.WebContent [1017]

Path: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/XPCServices /com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

Identifier: com.apple.WebKit.WebContent

Version: 11603 (11603.1.30.0.34)

Build Info: WebKit2-7603001030000034~7

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Safari [1001]

User ID: 501

Date/Time: 2017-03-31 20:16:21.071 +0200

OS Version: Mac OS X 10.11.6 (15G1421)

Report Version: 11

Anonymous UUID: AA5EF7D8-BA31-92D4-E17F-D3876FD5952E

Time Awake Since Boot: 180 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0:

-->

__TEXT 000000010d10c000-000000010d10e000 [ 8K] r-x/rwx SM=COW /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/XPCServices /com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

Application Specific Information:

Bundle controller class:

BrowserBundleController

Global Trace Buffer (reverse chronological seconds):

11.498403 AppleJPEG 0x00007fff8a6efa11 [0x7f83f5042400] Releasing session

11.501330 AppleJPEG 0x00007fff8a6efa11 [0x7f83f5036e00] Releasing session

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.WebCore 0x000000010eb13d17 WebCore::GraphicsContext::platformContext() const + 7

1 com.apple.WebKit 0x000000010d2d7ccb WebKit::WebDragClient::startDrag(***::RetainPtr<NSImage>, WebCore::IntPoint const&, WebCore::IntPoint const&, WebCore::DataTransfer&, WebCore::Frame&, bool) + 191

2 com.apple.WebCore 0x000000010efd700e WebCore::DragController::doSystemDrag(***::RetainPtr<NSImage>, WebCore::IntPoint const&, WebCore::IntPoint const&, WebCore::DataTransfer&, WebCore::Frame&, bool) + 270

3 com.apple.WebCore 0x000000010efd6eab WebCore::DragController::startDrag(WebCore::Frame&, WebCore::DragState const&, WebCore::DragOperation, WebCore::PlatformMouseEvent const&, WebCore::IntPoint const&) + 5947

4 com.apple.WebCore 0x000000010ecbeb74 WebCore::EventHandler::handleDrag(WebCore::MouseEventWithHitTestResults const&, WebCore::CheckDragHysteresis) + 2420

5 com.apple.WebCore 0x000000010ec24cbc WebCore::EventHandler::handleMouseDraggedEvent(WebCore::MouseEventWithHitTestRe sults const&) + 60

6 com.apple.WebCore 0x000000010ec22343 WebCore::EventHandler::handleMouseMoveEvent(WebCore::PlatformMouseEvent const&, WebCore::HitTestResult*, bool) + 1427

7 com.apple.WebCore 0x000000010ec21bd9 WebCore::EventHandler::mouseMoved(WebCore::PlatformMouseEvent const&) + 169

8 com.apple.WebKit 0x000000010d146fd7 WebKit::WebPage::mouseEvent(WebKit::WebMouseEvent const&) + 535

9 com.apple.WebKit 0x000000010d3248b6 void IPC::handleMessage<Messages::WebPage::MouseEvent, WebKit::WebPage, void (WebKit::WebPage::*)(WebKit::WebMouseEvent const&)>(IPC::Decoder&, WebKit::WebPage*, void (WebKit::WebPage::*)(WebKit::WebMouseEvent const&)) + 84

10 com.apple.WebKit 0x000000010d1fbbe3 IPC::MessageReceiverMap::dispatchMessage(IPC::Connection&, IPC::Decoder&) + 113

11 com.apple.WebKit 0x000000010d369b02 WebKit::WebProcess::didReceiveMessage(IPC::Connection&, IPC::Decoder&) + 28

12 com.apple.WebKit 0x000000010d1c2ffb IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >) + 119

13 com.apple.WebKit 0x000000010d1c57fc IPC::Connection::dispatchOneMessage() + 126

14 com.apple.JavaScriptCore 0x000000010e7a19f9 ***::RunLoop::performWork() + 169

15 com.apple.JavaScriptCore 0x000000010e7a1cb2 ***::RunLoop::performWork(void*) + 34

16 com.apple.CoreFoundation 0x00007fff919207e1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

17 com.apple.CoreFoundation 0x00007fff918fff1c __CFRunLoopDoSources0 + 556

18 com.apple.CoreFoundation 0x00007fff918ff43f __CFRunLoopRun + 927

19 com.apple.CoreFoundation 0x00007fff918fee38 CFRunLoopRunSpecific + 296

20 com.apple.HIToolbox 0x00007fff99680935 RunCurrentEventLoopInMode + 235

21 com.apple.HIToolbox 0x00007fff9968076f ReceiveNextEventCommon + 432

22 com.apple.HIToolbox 0x00007fff996805af _BlockUntilNextEventMatchingListInModeWithFilter + 71

23 com.apple.AppKit 0x00007fff8f93edf6 _DPSNextEvent + 1067

24 com.apple.AppKit 0x00007fff8f93e226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

25 com.apple.AppKit 0x00007fff8f932d80 -[NSApplication run] + 682

26 com.apple.AppKit 0x00007fff8f8fc368 NSApplicationMain + 1176

27 libxpc.dylib 0x00007fff980d3194 _xpc_objc_main + 795

28 libxpc.dylib 0x00007fff980d1bbe xpc_main + 494

29 com.apple.WebKit.WebContent 0x000000010d10d7c0 0x10d10c000 + 6080

30 libdyld.dylib 0x00007fff8a74d5ad start + 1

Mac Pro, OS X El Capitan (10.11.6), MacPro3,1 2,8 GHz 32 GB ram

Posted on Mar 31, 2017 12:48 PM

Reply

Answer 1

Top-ranking reply

touchMe

Level 1

19 points

May 1, 2017 11:15 AM in response to twrmark

Maybe try this...

I am on late 2015 iMac w/Retina, El Capitan 10.11.6, Safari 10.1

System Preferences > Displays > Color (default is iMac)
Change profile to sRGB IEC61966-2.1
Now try dragging and dropping

Lower brightness on keyboard by a couple of notches and color is (almost) perfect match for iMac profile

Reply

Answer 2

Eric Root

Level 10

684,597 points

Apr 1, 2017 9:03 AM in response to twrmark

Several people have had the same problem, so it may be a bug.

Send Apple feedback. They won't answer, but at least will know there is a problem or a suggestion for change. If enough people send feedback, it may get the problem/suggested change solved sooner.

Feedback

Reply

Answer 3

Eric Root

Level 10

684,597 points

Apr 1, 2017 9:21 AM in response to DanieleMarchi

On the computer(s) where you are having problems, try running the combo update. It installs all previous updates plus the new one, which can replace any files that may have become corrupted.

macOS Sierra 10.12.4 Combo

Reply

Answer 4

Bob Mayo

Level 2

150 points

Apr 7, 2017 10:32 AM in response to twrmark

I've been having problems with dragging from Safari -- no crashes, but not working. Here's my situation, in case the info helps in addressing your problem:

Drag & Drop not working; mac Bluetooth hardware problem, macOS issue, or both?

Reply

Answer 5

Eric Root

Level 10

684,597 points

May 2, 2017 7:19 AM in response to Pablo Olmos

Apple doesn’t routinely monitor the discussions. These are mostly user to user discussions.

Send Apple feedback. They won't answer, but at least will know there is a problem or a suggestion for change. If enough people send feedback, it may get the problem/suggested change solved sooner.

Feedback

Reply

Answer 6

Mar 31, 2017 2:56 PM in response to twrmark

Yes but we have no way of knowing what you've tried that didn't work unless you tell us.

Try deleting the cache ...

Open the Finder. From the Finder menu bar click Go > Go to Folder

Then copy / paste the following:

~/Library/Caches/com.apple.Safari

Then click Go and move the Cache.db file to the Trash.

Quit and relaunch Safari to test.

Reply

Answer 7

Apr 4, 2017 6:25 PM in response to twrmark

same problem here.... el capitan. 24 inch 2007 iMac....

was fine before... irritating that you can not rollback

safari crash when dragging any image/text (A problem occurred with this page so it was reloaded.)

Reply

Answer 8

Apr 14, 2017 2:46 PM in response to BankDadio

I had to get back Safari 10.0.3 by using Time Machine backups to roll it back to mid March to the state of my system on a day before I made the update to Safari. If you go for a re-install of the OS itself, it won't go back to that version. I have had three days of conversations about this with AppleCare call centre. At third level of escalation, senior technician engineer, was a lot brighter than the usual front line call takers. She had not heard of this bug yet, but took a screenshot of the error report that comes up, acknowledged it is worth putting it to their engineers. She told me she has the special feedback/report forms and authority to do this, not visible on the public forums and above the level of the Apple feedback forms we the public can access. She said when she sends up these forms, the engineers have to respond. So let's see what they come up with. I suspect they will quietly roll out a further update.

Reply

Answer 9

leveli

Level 1

13 points

Apr 26, 2017 8:17 AM in response to twrmark

I'm using OS X Capi 10.11.6 and Safari 10.1, and it seems any drag and drop action on HTML content inside Safari is provoking a crash:

* Select text and drag the selection? Crash

* Drag image? You betcha it crashes

* Drag hyperlink? Guess what: Crash

Not affected: interactive objects programmed to be draggable, like dragging an email item to the trash in GMail.

I think we need to send those Safari crash reports and Feedback forms to Apple so they can fix this in a subsequent Safari release.

Reply

Answer 10

leveli

Level 1

13 points

May 1, 2017 12:02 PM in response to touchMe

This sounds like it cannot possibly work but does.

I tested all of the color profiles in my MBP and verified the ones that do work are Display, Duet Display, Generic RGB Profile, HD 709-A, Rec. ITU-R BT.2020-1, and sRGB IEC61966-2.1. All the others make Safari crash. I also tested doing drag and drop in Safari using integrated and discrete GPU and changing color profiles to see if it made a difference, but it didn't.

Reply

Answer 11

May 1, 2017 1:19 PM in response to touchMe

Weird, this seems to have worked for me as well on my rMBP. I selected the "sRGB IEC61966-2.1" profile and then tested Safari and no crash. I changed the profile back to the default the "Color LCD" profile and Safari is still not crashing. Now that I think of it, I wonder if Safari ever crashed when I did this on the rMBP display.

So, I moved my Safari window to my TB attached Asus external display. Crash. Changed profile to "sRGB IEC61966-2.1". No crash. Changed profile back to "Asus PB278". Crash.

So, I have left the profile for my external monitor as "sRGB IEC61966-2.1" for the time being.

Thank you for the work around.

Reply

Answer 12

May 2, 2017 3:44 AM in response to twrmark

The same problem here!! 😟

Safari 10.1

El Capitan 10.11.6

MacPro early 2008, 2 x 3 GHz Quad-Core Intel Xeon, 8 GB 800 MHz DDR2 FB-DIMM, ATI Radeon HD 5770 1024 MB, SSD drive OWC 1Tb system hard drive...

Erase caché, stop all the run extensions on safari...

But the problem is there, crash when I drag an image to copy in a folder finder.

I think that Chrome is my next web browser. Safari is dead for me! 😠

I'm very tired on click second mouse bottom and save as... find the folder and bla bla bla... it's a...

Apple, are you kidding me? 😠

Reply

Answer 13

touchMe

Level 1

19 points

May 2, 2017 9:31 AM in response to codegard

I wish someone could explain it to me also codegard. I can only relate to you what I was able to discover from the error code output (I am not an engineer). It would seem there is a definite bug in Safari 10.1 as it relates to the display (specifically Retina), when we try and drag and drop the error indicates that Safari is trying to access a non existent memory location, further investigation of the error code seems to indicate that this has 'something' to do with display. Folks here and on other threads have been mentioning that drag and drop was working on some external monitors, drag and drop works on my MBAir, but not my iMac/retina... so changing the color profile might (and does) 'fool' the OS as a workaround. It is not a solution, for some folks color profile is critical. I prefer the the iMac profile but the suggested change comes close. Maybe if you or others are speaking to Apple support, these clues can be related to them?

Reply

Answer 14

igirl1

Level 1

105 points

May 2, 2017 10:12 AM in response to touchMe

touchMe wrote:

It is not a solution, for some folks color profile is critical.

Waves...

I'm a professional photographer and depend on having my monitors calibrated (custom). Those profiles do not work for the band aid solution. Besides which, the suggested color profiles for the fix, look really bad to me. 😕

Reply

Answer 15

codegard

Level 1

9 points

May 2, 2017 10:17 AM in response to igirl1

I do strongly agree. I regularly re-calibrate my monitor to ensure color selection and color correction are accurate. My appreciation for the Displays bug information was directed toward the fact that the source of the bug has apparently been identified. I may actually use the alternative profile when working with web-based, drag-and-drop interfaces in Safari, and switch back to my calibrated display profile when using photoshop, etc.

Reply