Hey @berendjanwever , by any chances do you have any NULL pointer defer crashes for Chrome? Testing some python code, thanks :)
-
-
That's brilliant, thanks so much, should have asked before messing with the subprocess hell. Will definitely use that, thanks cheers!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Fuzzzing happens during step 4 for me: browser makes request, server generates JS on the fly and sends it in response, browser eval()s it and returns results, repeat until crash. If no crash after N rounds, call fStop() and start cleanly
-
I am doing more or less the same, with the exception that I'm storing the cases in an array (a bit slow but it works) as I don't want to mess with JS stuff. Out of curiosity after how many rounds do you start cleanly?
-
That depends on various factors. If each round is large, the combined repro file becomes large quickly, less rounds are advised. If I require a lot of state to build-up, more rounds are needed. In general I pick a random number from a range based on educated guessing.
-
Brilliant, that makes sense! Thanks again!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

Working on how to catch those crashes with python twisted/subprocess ain't that easy!