Bug #13129 select * from information_schema.routines gives out of memory error

• Submitted: 13 Sep 2005 5:19
• Modified: 14 Sep 2005 1:21
• Reporter: Ritesh Nadhani
• Status: Can't repeat
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.0.12-beta-nt |
• OS: Windows (Windows)
• CPU Architecture: Any

[13 Sep 2005 5:19] Ritesh Nadhani

Description:
Doing a select * from information_schema.routines in 5.0.12 throws up an out of memory error.

I think it was not there in 5.0.10.

How to repeat:
mysql> use information_schema;

Database changed

mysql> select * from routines limit 0, 40;

ERROR 5 (HY000): Out of memory (Needed 1492451408 bytes)

mysql> select version();

+----------------+

| version()      |

+----------------+

| 5.0.12-beta-nt |

+----------------+

1 row in set (0.00 sec)

[13 Sep 2005 6:50] Valeriy Kravchuk

Thank you for your bug report. But I was unable to repeat it:

mysql> select version();
+----------------+
| version()      |
+----------------+
| 5.0.12-beta-nt |
+----------------+
1 row in set (0.05 sec)

mysql> use information_schema;
Database changed
mysql> select * from routines limit 0, 40;

... (skipped the results)

6 rows in set (0.79 sec)

So, in a simple case everything works as expected. We need more information to verify this as a bug.

How many stored procedures do you have?
Are there any messages in the log (<hostname>.err file in the data directory, by default)?
What hardware do you use (amount of RAM?)

Please, send your my.ini file also. The message in your case stated you needed about 1.5 Gb of memory. We should figure out why.

[13 Sep 2005 7:00] Ritesh Nadhani

I have absolutely no problem sendind you data. I can just zip the whole data directory to an FTP site of your choice. But most of the data are in InnoDB so how do you want to have the backup?

The machine is WinXP with 512 MB RAM.

I will attach my.ini later today.

[13 Sep 2005 12:04] MySQL Verification Team

Also did you upgrade 5.0.12 over an older version 5.0.9?.
In short your SP, functions, triggers were created with the older
version?

Thanks in advance.

[13 Sep 2005 13:53] Ritesh Nadhani

Yes. Indeed I upgraded from 5.0.10 to 5.0.12. The good this is that once I did a clean reinstall, the problem went off. So I guess it was an upgrading issue.

Is this documented anywhere?

[14 Sep 2005 1:21] MySQL Verification Team

I was unable to repeat the behavior reported, creating some SP
on version 5.0.10 and then upgrade to 5.0.12.

[14 Sep 2005 2:20] Ritesh Nadhani

Even I am not able to reproduce the issue. I guess it was a problem on my side. I guess you can close this bug.