Tab crashing/freezing in Google Chrome
I'm using Google Chrome 15.0.874.121, running on Ubuntu Linux 10.04.
Sometimes, when a new task is being added, at the point where Checkvist would normally expand the text box automatically as I type, the whole browser tab becomes unresponsive.
I can work-around this by hitting Return after a few words (before the text box would be auto-expanded) and then double-E to edit the item and add the rest of the sentance. The bug only seems to hit for items that are being newly added.
Latest fixes were put to http://checkvist.com
-
Thanks Nick, the fix is already on http://checkvist.com :)
-
Nick commented
Kirill I just checked the beta.checkvist.com site and the bug is fixed for me now! Thanks so much, I can switch back from gmail tasks now!
-
Has anybody tried the latest fix on the beta.checkvist.com site?
Thanks! -
Steven Zins commented
I see Mark Nielsen sees it working perfectly. Sorry to report that I still have the same freeze on beta.checkvist.com . It still looks like edit field overflow freezes iff no focus.
-
Nick commented
The long sub item in this list has the problem 100% of the time for me:
http://beta.checkvist.com/checklists/97303-test-list -
Nick commented
I am definitely still able to reproduce the bug on the beta site. It seems to only happen when you try to edit an item that is already longer than the default text box would be.
-
Mark, thanks a lot for the good news and for your help!
I'll ask some more users who had the problem to verify the fix, and after that will send the fix to the production server.
-
Mark Nielsen commented
This seems to work perfectly. I can't cause the crash on the beta.checkvist.com site now - and I tried *really* hard :)
And, of course, I can still cause the bug on the main, non-beta site. So there's nothing in my local environment that is causing the difference on beta site.
So I reckon you've fixed it, Kirill. Nice one :)
-
Mark, thanks a lot for the additional data, will try to use it later today to research the problem.
-
Mark Nielsen commented
OK - it's getting better. It's working some of the time now, under specific circumstances. I can tell when a new item is going to work fine and when it's going to crash the tab because there is a difference in the input's border style. There's a picture here to demonstrate: http://flet.org/img/c/checkvist-bug4.jpg
When I use Shift+Return to create a nested item, I get a "softer" border style around the input, and I know that it will expand properly. Also, after that Shift+Return, any items I add immediately after without changing my position in the list will also work just fine.
However, if I change my position in the list and add a new item with a normal Return key, the border around the new item will be a solid, square and black, and typing past the point where the input should expand will cause the bug and the tab will crash.
I have to admit, I don't know if this behaviour is different to yesterday, because I didn't test it so thoroughly yesterday. However, at least this adds a bit more data. When you use Shift+Return, something different is happening in the app that doesn't cause the bug. After that, changing your position and using plain Return to add a new item triggers the bug.
Cheers!
-
Mark Nielsen commented
Just to confirm - I did refresh my browser before trying all that. If there's anything else I should/can do, please let me know.
-
Mark Nielsen commented
The bug still seems to be there. I've attached some screen shots, captured during the process. As the text I type gets longer than the box, it tries to wrap around (rather than the box stretching out to the right). The crash happens at exactly the moment where the text wraps to the second line.
Sceenshots here:
http://flet.org/img/c/checkvist-bug1.jpg
http://flet.org/img/c/checkvist-bug2.jpg
http://flet.org/img/c/checkvist-bug3.jpgGood luck with it, Kirill, and thanks for the speedy response. Very much appreciated.
-
Hello Mark,
The bug is not Linux - only, it reproduces on Windows as well. Unfortunately, I wasn't able to reproduce it, but I've rewritten a bunch of the related code, so the problem may be fixed. I'd appreciate if you let me know whether my fix works for you.
Thanks!
-
Mark Nielsen commented
Thanks Kirill. I'd be surprised if this was a Linux-only issue. I'd have thought Chrome behaves just the same on any platform. Still, I'm no JS expert. If you really need to test on Ubuntu, you can always use http://crossbrowsertesting.com. I use this to avoid the pain of installing Windows ;) and it's great.
In the meantime, I'll stick to my workaround. I don't fancy running two browsers, or installing unstable software which might cause me headaches in other places.
-
Hello Mark,
Thanks for the bug report. Unfortunately, we don't have a Linux installation at hands, so it will take some time until we install Ubuntu and reproduce the problem. In the meantime, I'd suggest using another browser with Checkvist, either another version of Chrome (from beta channel, for instance), or Firefox.
Thanks again,
KIR