Erik, could you have a look at this one? Could this be related to your ia32 bit ops changes?

 Issue 52183  has been merged into this issue.

Is there any movement on this?

The fix for this has just been pushed to tip of tree chromium this morning.

 Issue 52214  has been merged into this issue.

 Issue 52490  has been merged into this issue.

Pushing this bug into the latest Dev channel release is very frustrating.  Would you consider saving us hundreds of support hours and tons of user frustration by fixing this sooner rather than later in the dev channel?  Is it going to be pushed to the beta channel too? 

We are now getting many many support emails that people are now experiencing this with 6.0.495.0 dev.

Did the fix make it into that build?
If so, then it does not fix the problem.

Personally, I can now log into LastPass, but the test page mentioned above still fails.

Is there a way to escalate this problem, we are really being impacted badly by it.

Here's a solution that worked for me for a temporary workaround.  Either sync your settings or save a backup copy of your Default User Date File, on xp it's at C:\Documents and Settings\%user%\Local Settings\Application Data\Google\Chrome\User Data\Default and then go to filehippo.com (they have previous versions of dev/beta and stable releases). Uninstall your current version first. I am sticking with dev version 6.0.427.33 for now as I am confident that it works perfectly with last pass.  Hope this helps.

We've pushed LastPass version 1.69.8+ which will inform you when you're using a browser with this bug.

The Javascript engine can't do math correctly so you shouldn't use this version of the browser -- please update to 1.69.8+ and restart chrome and hopefully you'll get a notice if there's an issue with your browser

When can we expect an update to Chrome/Chromium to be pushed out to fix this issue?  It's getting extremely aggravating.

Additionally, to the lastpass guys, can you warn people on your site's login area about this issue, or at least have a warning display to anyone with a chrome 6 user agent?  It'd save you guys a few emails, that's for sure.

To people who say that this is not fixed: Yes it is. Try the latest version of Chromium.

EXPECT things break now and then. Screaming and ranting about problems on a dev channel is evidence that you should not be using a dev channel.

Fixes get made in CHROMIUM and rolled to the Google CHROME dev channel later.

I can confirm that the problem goes away for me in the nightly Chromium (7.0.498.0 (56485))

Yup, confirmed fixed in every case on chromium nightly 7.0.498.0 (56483), thanks Erik.

If you use Windows:

Uninstall the dev build.
Install the latest stable build from http://www.google.com/chrome
Install Chrome Canary from http://tools.google.com/dlpage/chromesxs (more frequently updated than the dev channel, runs side by side with any other Chrome build)

This was fixed in V8 version 2.3.8. As far as we know, only V8 version 2.3.7 has this problem. It was fixed in chromium in revision 56316. This issue has therefore been fixed and marked as such. It will hit the releases soon.

If you have a problem with V8 2.3.8 or 2.2.x.y, please file a separate bug report and cc me on it (ager@chromium.org).

Thanks.

http://www.chromium.org/getting-involved/dev-channel#TOC-Going-back-to-a-more-stable-channel

 Issue 52559  has been merged into this issue.

 Issue 52571  has been merged into this issue.

 Issue 52640  has been merged into this issue.

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

(No comment was entered for this change.)

(No comment was entered for this change.)