Queries fail to execute, localStorage key full

[robd003]

Seeing this error in DevTools Console:

QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'crate.console.query_list' exceeded the quota.
    at updateRecentQueries (app.bundle.js:47517:24)
    at self.execute (app.bundle.js:47629:9)
    at $scope.execute (app.bundle.js:47676:14)
    at fn (eval at compile (vendor.bundle.js:25096:15), <anonymous>:4:141)
    at callback (vendor.bundle.js:37671:13)
    at ChildScope.$eval (vendor.bundle.js:28071:28)
    at ChildScope.$apply (vendor.bundle.js:28170:25)
    at HTMLDivElement.<anonymous> (vendor.bundle.js:37675:19)
    at defaultHandlerWrapper (vendor.bundle.js:12439:11)
    at HTMLDivElement.eventHandler (vendor.bundle.js:12427:9)

This is on Crate 6.2.2 & 6.2.3

Maybe do something like this and start evicting the oldest records in query_list when localStorage gets near 5mb:

function getLocalStorageUsedBytes() {
  return Object.entries(localStorage).reduce((total, [key, value]) => {
    return total + (key.length + value.length) * 2; // UTF-16 = 2 bytes/char
  }, 0);
}

[amotl]

Hi Robert,

thank you very much for reporting this. Do you have the feeling that the localStorage is filling up faster on CrateDB 6.2.2 or 6.2.3? We didn't change anything on Admin UI afaik, so I guess it will be more related to the fact that you are a long-term and power user of CrateDB and its Admin UI?

Thank you for sharing an idea how to mitigate the problem with code. Did you find any workaround to clear the localStorage manually, either per UI, or by invoking a little snippet on the JavaScript Console? If other users are running into the same problem, I think it will be good to share an ad hoc mitigation recipe with them.

With kind regards,
Andreas.

[robd003]

@amotl I was able to clear localStorage manually and get the admin UI working again, but it just sucks that a user would have to be knowledgable enough to do that.

[amotl]

@bgunebakan, @matriv: This issue can likely hurt others as well. Can you possibly look into it if you have some spare minutes / flag it as a bug if you agree?