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

Anyone got any technical details about this? Judging from the "trap backfired" link posted elsewhere in the comments, somehow Chrome can ensure the specific flash crash ends up accessing invalid memory at 0xABAD1DEA... but how?


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

Search: