I can confirm now the bug is gone. I have tested 32-bit jaunty and 64-bit lucid with both Chromium 5.0.395.0 and 5.0.396.0. There is no bug anymore. So this suggests the version 5.0.393.0 was an unlucky one.
I can confirm now the bug is gone.
I have tested 32-bit jaunty and 64-bit lucid with both Chromium 5.0.395.0 and 5.0.396.0.
There is no bug anymore.
So this suggests the version 5.0.393.0 was an unlucky one.