«

webkit + forks be warned

This is just a quick post to alert you to an interesting edge case I came across, while creating one of my next small products like emgen.io.

It's a bug I've confirmed effects the latest version of both safari and chrome and I assume that it also effects mobile versions of the bing and webkit browsers.

Here's the deal, if you're doing pushState based history modification in the browser and you accidentally introduce an infinite loop, you're going to have a bad time.

It seems to be that the usual Chrome catches to see if there's a runaway process or javascript function seem to be getting passed because (and I'm just assuming here) the browserState is something that is not held directly inside the child process for the tab but rather held in the main process, causing it to hang somewhat.

Pretty Crazy huh?

Anyway, I doubt many people will come across this but hopefully you find this before the bug finds your app.

Share Comment on Twitter