News for hackers. Stuff that matters.

A comment on On the Worst-Case Complexity of TimSort. Parent comment

Re:On the Worst-Case Complexity of TimSort by mcherm on Friday August 31, 2018 @09:53AM (#17885559)
Causing a crash is an excellent vector for a denial-of-service attack.
[ Parent | on HN ]
Re:On the Worst-Case Complexity of TimSort by alexeiz on Friday August 31, 2018 @10:37AM (#17885925)
If you can make your service allocate 10G of memory, it's already a denial of service attack.
[ Parent | on HN ]
Re:On the Worst-Case Complexity of TimSort by vbezhenar on Friday August 31, 2018 @12:02PM (#17886633)
Usually unexpected exception results in a HTTP 500 response (or something similar) and few lines in the log. It does not result in stopped server.
[ Parent | on HN ]
Re:On the Worst-Case Complexity of TimSort by ryeguy on Friday August 31, 2018 @01:34PM (#17887402)
It's an exception, not a crash.
[ Parent | on HN ]