135790 2014-08-10 11:04:26 -0700 WebContent crashes when scrolling in www.facebook.com 2014-08-18 09:19:23 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Mac OS X 10.9 RESOLVED FIXED InRadar P1 Normal --- 1 sparkles3020 webkit-unassigned ap bshafiei ggaren mark.lam morbius msaboff simon.fraser sparkles3020 oldest_to_newest 1028103 0 sparkles3020 2014-08-10 11:04:26 -0700 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. 1028104 1 sparkles3020 2014-08-10 11:11:52 -0700 I am using webkit nightly version r172379. 1028295 2 ap 2014-08-11 13:41:56 -0700 Yes, I can easily reproduce in trunk. 1028297 3 ap 2014-08-11 13:43:22 -0700 <rdar://problem/17981353> 1028908 4 sparkles3020 2014-08-13 14:17:35 -0700 Same facebook bug still present in webkit build r172516. 1029066 5 sparkles3020 2014-08-14 05:10:47 -0700 Same facebook bug still present in webkit build r172577. 1029103 6 ap 2014-08-14 09:26:05 -0700 Thank you for following up. There is no need for an update unless something changes, we do track this bug. 1029117 7 sparkles3020 2014-08-14 09:53:45 -0700 Thank you. Any timeline for a fix? 1029288 8 morbius 2014-08-14 18:57:04 -0700 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. 1029293 9 sparkles3020 2014-08-14 19:26:37 -0700 I can only hit the arrow key 3 or 4 times before it starts reloading. I agree it is making the nightly unusable. 1029456 10 mark.lam 2014-08-15 13:45:26 -0700 I can’t seem to reproduce this with a release build of r172640. I was able to reproduce it with 172549 earlier. 1029460 11 morbius 2014-08-15 13:56:25 -0700 This now seems to be fixed. Yay!