News for hackers. Stuff that matters.

A comment on When “Dumb Pipes” Get Too Smart.

Re:When “Dumb Pipes” Get Too Smart by lanius on Friday February 24, 2017 @07:46PM (#13729315)
Has the WebCore scheduler improved since?
[ Parent | on HN ]
Re:When “Dumb Pipes” Get Too Smart by edoceo on Saturday February 25, 2017 @12:19AM (#13730210)
The bug is in bad js authored by CF hammering ticks/event-loop.

WebCore is doing what it's told, just just being told very stupid things (very, very quickly)

[ Parent | on HN ]
Re:When “Dumb Pipes” Get Too Smart by chainsaw10 on Saturday February 25, 2017 @01:37AM (#13730404)
> The bug is in bad js authored by CF

No, the bug is definitely in the browser. Web code is untrusted and should not be able to adversely affect the browser.

[ Parent | on HN ]
Re:When “Dumb Pipes” Get Too Smart by saurik on Saturday February 25, 2017 @02:01AM (#13730459)
So, there was (I hope not "is"... I am having a difficult time remembering the sequence of events involving this bug and what I might have done on the WebKit side) definitely a bug in the browser, but just to be explicit: there was also a bug in the JavaScript (the array returned as object with no length, causing the code to loop), and managing to deploy a change that managed to DoS tons of deployed browsers and somehow not noticing and then not really caring afterwards was extremely careless.
[ Parent | on HN ]