‘too much time spent in unload handler’ – chrome error
Bumped into this error while invoking a webcal link (and staying on the same page). Apparently clicking the link starts a sequence that eventually fires onbeforeload, which in its turn causes the error.
Reports of this bug first popped in search near the end of February January and probably related to a recent chrome build (Chrome Version : 4.0.249.89, Official Build 38071). After letting the issue for few days, I did some extra searching today and came up with a tweet by @rvdavid:Held up by a “Too much time spent in unload handler.” error on #chromium. in trying to find solutions, All I find “unconfirmed” #bug reports. Replying to the tweet led me to a possible solution by the Chrome team. As far as I understand we may see the solution already merged into one of the next official releases. Will update.
XMarks for chrome alpha 0.4.19
I’m a heavy user of XMarks as I use 3 different browsers, each one for it’s purpose (IE for testing at work when we are developing for mainly IE, FF for general dev and Chrome for fast Internet :)).
XMarks has now entered the alpha stage for the Chrome plug-in. I tested it on Chrome 4.0.206.1 and it works great so far.
