Bug #11070 | GLib-ERROR **:gmem.c:173: failed to allocate 22720000 bytes | ||
---|---|---|---|
Submitted: | 3 Jun 2005 11:40 | Modified: | 4 Sep 2006 12:59 |
Reporter: | Oliver Peters | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.1.9 | OS: | Windows (Windows2000) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[3 Jun 2005 11:40]
Oliver Peters
[3 Jun 2005 11:42]
Oliver Peters
it's 3.8 million records (sorry, forgot the million)
[3 Jun 2005 16:04]
Michael G. Zinner
The problem is that you run out of memory on your local machine. You might want to limit the number of returned rows with the LIMIT statement. Nevertheless the error message should be more desciptive and be printed inside the normal error table. We are going to auto limit the number of returned rows to a percentage of the available main memory, e.g. 40%. If the number of rows fetched require more memory than that, we will print the error message.
[4 Sep 2006 12:59]
Alfredo Kojima
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/