That is likely chrome.storage's silent quota limit. I am releasing an update to 3.1, which fixes silent failures and adds more storage room. If the failure persists, open a GitHub issue on the support site and fix it.