Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Looks like it's not load that brought it down but someone posting a 340kb individual message that's triggering a bug because we didn't account for that sort of thing somewhere.

The good thing is we now have an easily reproducible case, thanks HN :)



Update: it was something else entirely, that we worked around for now and will fix soon


what was the other thing that brought it down!? Please don't leave us hanging!!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: