Working workaround for the Chrome storage issue

Some odd Chrome behaviour made me think the code was throwing an error.
In fact it was just badly-worded debugging information.  The real issue
was chrome.storage.local.get() being super-slow (and perhaps timing out).

This workaround uses the fallback implementation if it detects a timeout.