| Bug #13389 | Sidebar causes out-of-memory (system crash) by loading column data | ||
|---|---|---|---|
| Submitted: | 21 Sep 2005 21:40 | Modified: | 5 Oct 2005 16:00 |
| Reporter: | J Jorgenson | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S2 (Serious) |
| Version: | 1.1.14 | OS: | Windows (WinXP) |
| Assigned to: | CPU Architecture: | Any | |
[21 Sep 2005 23:16]
Jorge del Conde
Thanks for your bug report. This bug can easily be reproduced with 3000 tables.
[13 Mar 2014 13:34]
Omer Barnir
This bug is not scheduled to be fixed at this time.
Description: I've got a database with 13000 tables... (Yes, I'm doing database Data Mining/Warehouse) This # is going to grow EASILY to 26,000+ tables. When loading all 13000 tables, the RAM used by Query Browser causes a SYSTEM CRASH. After watching my connection from the Admin tool, the issue is because EVERY table is "described", loading column & key info into the sidebar. The result is all available RAM is exhausted (512meg RAM). How to repeat: Create LOTS (10,000+) of tables with a variation of 30-135 columns each table. Suggested fix: a) Support 'on-the-fly' loading of the table's columns in the sidebar. ex: Load the column details ONLY for a table, WHEN selected. b) Provide a setting to 'NOT load the columns' for each table in the sidebar. ex: Display only the list of tables, And NOT load the columns details for each table. c) Do not auto-load 'columns' for sidebar when > 100(50?) tables exist in the database. If you can support a mixture of 'on-the-fly' column loading and a 'pre-load columns app setting', this would be ideal.