Bug 135790

Summary:	WebContent crashes when scrolling in www.facebook.com
Product:	WebKit	Reporter:	sparkles3020
Component:	JavaScriptCore	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	ap, bshafiei, ggaren, mark.lam, morbius, msaboff, simon.fraser, sparkles3020
Priority:	P1	Keywords:	InRadar
Version:	528+ (Nightly build)
Hardware:	Mac
OS:	OS X 10.9

Description sparkles3020 2014-08-10 11:04:26 PDT

This problem started on Aug. 4.  When I try to scroll, I get the following message:

A problem repeatedly occurred with https://www.facebook.com reload webpage.

If I reload, the same behavior occurs over and over, making website unusable.

I searched for Facebook bugs, and could not find a new bug reported.

Comment 1 sparkles3020 2014-08-10 11:11:52 PDT

I am using webkit nightly version r172379.

Comment 2 Alexey Proskuryakov 2014-08-11 13:41:56 PDT

Yes, I can easily reproduce in trunk.

Comment 3 Alexey Proskuryakov 2014-08-11 13:43:22 PDT

<rdar://problem/17981353>

Comment 4 sparkles3020 2014-08-13 14:17:35 PDT

Same facebook bug still present in webkit build r172516.

Comment 5 sparkles3020 2014-08-14 05:10:47 PDT

Same facebook bug still present in webkit build r172577.

Comment 6 Alexey Proskuryakov 2014-08-14 09:26:05 PDT

Thank you for following up. There is no need for an update unless something changes, we do track this bug.

Comment 7 sparkles3020 2014-08-14 09:53:45 PDT

Thank you.  Any timeline for a fix?

Comment 8 Wade Smith 2014-08-14 18:57:04 PDT

Glad to see this bug reported. It's been doing this for awhile, and so far has not been repaired. If it's any consolation, it seems to be activate more rapidly while using a trackpad rather than the arrow keys or the page down/up keys. I've needed to stop using the Nightly because of this.

Comment 9 sparkles3020 2014-08-14 19:26:37 PDT

I can only hit the arrow key 3 or 4 times before it starts reloading.  I agree it is making the nightly unusable.

Comment 10 Mark Lam 2014-08-15 13:45:26 PDT

I can’t seem to reproduce this with a release build of r172640.  I was able to reproduce it with 172549 earlier.

Comment 11 Wade Smith 2014-08-15 13:56:25 PDT

This now seems to be fixed. Yay!