Troubleshooting Hanging Screen When Viewing Tables in MotherDuck via DuckDB UI on Localhost

·Sep 15, 2026 06:28 AM·

Hi, I have only just started using MotherDuck via the DuckDB UI. When I first attached a db, they were appearing fine when selected in the left sidebar and I could see the full list of tables. Now, when I attach a db, the query is running fine and the db is connected but I am getting a hanging screen / icon on the db when trying to view any of the tables of the attached db's. I have tried to use Claude to troubleshoot but have reached a dead end. I am using the UI on localhost:4213

👀1

8 comments

· Sorted by Oldest

Yahia M.
·
·
Thanks for the screenshots and description! Two things if you don't mind:
1.
While the sidebar is spinning, can you run select 1 in the query editor? Does it come back or does it hang too?
2.
Quit DuckDB completely (close the terminal it is running in) and start it again with duckdb -ui. Reloading the browser tab will not clear this, the process itself has to restart. Does the issue persist after restart?
If the tables come back after that, let me know which databases you had attached when it froze. The sidebar loads all of them together, so one that is slow to respond may slow down the whole list.
Xavier P.
·
·
Hi, I've done both of these things and it still hangs? When I first started using DuckDB on Sunday for the first time I was able to see all of the tables, but the past day I have not been able to
Yahia M.
·
·
Thanks for testing it! Looking at your new screenshot, MotherDuck looks like it is no longer connected in that session: my_db and sample_data have dropped out of the list, can you confirm if that is the case? Could you try this: In the editor, run ATTACH 'md:'; and then reload the page. Do my_db and sample_data come back, and does lhr list its tables?
Xavier P.
·
·
Still didn't work. I'm in MD, I can run a query, but the tables do not populate in the sidebar
👀2
Xavier P.
·
·
Yahia M.
·
·
Thanks for sharing the screenshots, taking a look!
🙏1

Yahia M.

Could you run these and paste back what you get, this will help figure out the any access issues to the schema:

SELECT schemata.schema_name, tables.table_name
FROM system.information_schema.schemata AS schemata
LEFT JOIN system.information_schema.tables AS tables
  ON tables.table_catalog = schemata.catalog_name
  AND tables.table_schema = schemata.schema_name
WHERE schemata.catalog_name = 'lhr';

and

SELECT extension_name, extension_version FROM duckdb_extensions() WHERE loaded;

will tell us the loaded extensions. Thanks!

Yahia M.
·
·
Also, do you have a ~/.duckdbrc file? If so, can you share its contents or any commands used there?

Troubleshooting Hanging Screen When Viewing Tables in MotherDuck via DuckDB UI on Localhost | MotherDuck Community

Yahia M.
·
·
Thanks for the screenshots and description! Two things if you don't mind:
1.
While the sidebar is spinning, can you run select 1 in the query editor? Does it come back or does it hang too?
2.
Quit DuckDB completely (close the terminal it is running in) and start it again with duckdb -ui. Reloading the browser tab will not clear this, the process itself has to restart. Does the issue persist after restart?
If the tables come back after that, let me know which databases you had attached when it froze. The sidebar loads all of them together, so one that is slow to respond may slow down the whole list.
Xavier P.
·
·
Hi, I've done both of these things and it still hangs? When I first started using DuckDB on Sunday for the first time I was able to see all of the tables, but the past day I have not been able to
Yahia M.
·
·
Thanks for testing it! Looking at your new screenshot, MotherDuck looks like it is no longer connected in that session: my_db and sample_data have dropped out of the list, can you confirm if that is the case? Could you try this: In the editor, run ATTACH 'md:'; and then reload the page. Do my_db and sample_data come back, and does lhr list its tables?
Xavier P.
·
·
Still didn't work. I'm in MD, I can run a query, but the tables do not populate in the sidebar
👀2
Xavier P.
·
·
Yahia M.
·
·
Thanks for sharing the screenshots, taking a look!
🙏1

Yahia M.

Could you run these and paste back what you get, this will help figure out the any access issues to the schema:

SELECT schemata.schema_name, tables.table_name
FROM system.information_schema.schemata AS schemata
LEFT JOIN system.information_schema.tables AS tables
  ON tables.table_catalog = schemata.catalog_name
  AND tables.table_schema = schemata.schema_name
WHERE schemata.catalog_name = 'lhr';

and

SELECT extension_name, extension_version FROM duckdb_extensions() WHERE loaded;

will tell us the loaded extensions. Thanks!

Yahia M.
·
·
Also, do you have a ~/.duckdbrc file? If so, can you share its contents or any commands used there?