Hi Christian, >From what I recall, when the problem was happening db:list() ! db:drop(.) >hung and db:list-details was slow to respond then gave an out of memory error.
The solution at the time was to delete all databases using an operating system command, since the databases are temporary in nature. That resolved the immediate problem, fortunately. However, I'm not able to inspect the files now to find the origin of the problem. If it's possible, if like to add more error logging, monitoring, or some way to identify if a database is corrupted, just in case any similar problem happens again. Thank you, Vincent This message was sent from a mobile device. Information Classification: General ________________________________ From: Christian Grün <[email protected]> Sent: Monday, September 29, 2025 4:44:42 AM To: Lizzi, Vincent <[email protected]>; Christian Grün via BaseX-Talk <[email protected]> Subject: AW: db:drop error not being caught Hi Vincent, > I encountered this specific error using BaseX GUI by running this script > while a database was open. I see: Mixing the GUI and other independent BaseX instances may indeed unexpected errors. > If db:list() is not working, is there any way to identify which databases > might be corrupt, locked, or somehow causing a problem? In principle, db:list() (without arguments) is nothing else than a file:list() operation for the database directory. You should be able to simulate it with: for $db in file:children(db:option('dbpath')) where file:is-dir($db) return file:name($db) Do you remember what happened when you tried to use db:list? Best, Christian
