Not surprising. The amount of aggressive caching that Chrome does to make the web "faster" is excessive, not to mention infuriating. Developing a web application and using Chrome is an exercise in anger management.

And then there's the bug in the dev channel where multiple assignment was just plain broken (bug report: http://code.google.com/p/chromium/issues/detail?id=136380)

Example:

    var foo = function() { /* foo function */ };
    var bar = function() { /* bar function */ };
    var baz = function() { /* baz function */ };
    var sup = function() { /* sup function */ };

    foo.test = bar.test = baz.test = sup;

    console.log(foo.test);  // shows bar, not sup