I have successfully identified the underlying issue at play here. By navigating to chrome://indexeddb-internals/ within your current Chrome browser session, you will notice that the impacted database has pending opens/deletes exceeding 0. This anomaly may stem from an incomplete transaction within that particular database. It is possible that attempts were made to delete or destroy the database, but these operations were not fully executed. As a result, your PouchDB instance (along with all other local PouchDB instances) becomes stuck in the initialization phase.
One potential solution is to restart your browser session, which should resolve the issue.
It would be highly beneficial if the team at PouchDB could incorporate a timeout observer functionality for initial indexedDB access. This observer could trigger an error callback if the indexedDB.open() method fails to respond within a specified time frame (e.g. 10 seconds). Such a feature would greatly assist developers in pinpointing the root cause of issues, rather than having to troubleshoot why PouchDB promises remain unresolved.