RESOLVED FIXED 135790
WebContent crashes when scrolling in www.facebook.com 
https://bugs.webkit.org/show_bug.cgi?id=135790
Summary WebContent crashes when scrolling in www.facebook.com
sparkles3020
Reported 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.
Attachments
Add attachment proposed patch, testcase, etc.
sparkles3020
Comment 1 2014-08-10 11:11:52 PDT
I am using webkit nightly version r172379.
Alexey Proskuryakov
Comment 2 2014-08-11 13:41:56 PDT
Yes, I can easily reproduce in trunk.
Alexey Proskuryakov
Comment 3 2014-08-11 13:43:22 PDT
<rdar://problem/17981353>
sparkles3020
Comment 4 2014-08-13 14:17:35 PDT
Same facebook bug still present in webkit build r172516.
sparkles3020
Comment 5 2014-08-14 05:10:47 PDT
Same facebook bug still present in webkit build r172577.
Alexey Proskuryakov
Comment 6 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.
sparkles3020
Comment 7 2014-08-14 09:53:45 PDT
Thank you. Any timeline for a fix?
Wade Smith
Comment 8 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.
sparkles3020
Comment 9 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.
Mark Lam
Comment 10 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.
Wade Smith
Comment 11 2014-08-15 13:56:25 PDT
This now seems to be fixed. Yay!
Note You need to log in before you can comment on or make changes to this bug.