UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36

Steps to reproduce the problem:
1. Create a simple extension to test chrome.storage functionality:

manifest.json:

{
  "name": "test extension",
  "version": "0.0.0.1",
  "manifest_version": 2,
  "content_scripts": [{
    "matches": ["*://www.example.com/*"],
    "js": ["script.js"]
  }],
  "permissions": [
    "storage",
    "*://www.example.com/*"
  ]
}

script.js:

chrome.storage.local.set({'key': 'value'});

document.body.addEventListener('click', function() {
  try {
    chrome.storage.local.get('key', function(items) {
      alert('callback invoked');
      alert(items['key']);
    });
  } catch(err) {
    alert('exception thrown');
    alert(err);
  }
}, false);

2. Open http://www.example.com/.

3. Observe that clicking anywhere on the page results in alerts showing 'callback invoked' and 'value', as expected.

4. Update the extension by pressing the reload button on chrome://extensions/. (Note: The same behavior occurs when updates are downloaded through the normal update process.)

5. Without reloading, click on the page again.

What is the expected behavior?
Either the call to chrome.storage.local.get should succeed, causing the same alerts as before updating the extension, or it should fail, still invoking the callback, but setting runtime.lastError.

What went wrong?
Observed behavior: Nothing happens. The callback is not invoked, and no exception is thrown.

WebStore page: 

Did this work before? No 

Chrome version: 51.0.2704.79  Channel: n/a
OS Version: 
Flash Version: 

Previously reported in
https://bugs.chromium.org/p/chromium/issues/detail?id=331059
but that issue is archived now.

Calling the set method after an update has similar behavior. The callback is not invoked, no exception is thrown, and no data is written to storage.