Bug #32474 | mysql vista c00005 appcrash | ||
---|---|---|---|
Submitted: | 17 Nov 2007 23:32 | Modified: | 19 Dec 2007 5:26 |
Reporter: | patrick joos | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S1 (Critical) |
Version: | 5.0.37 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysql vista appcrash c000005 |
[17 Nov 2007 23:32]
patrick joos
[18 Nov 2007 8:15]
Valeriy Kravchuk
Thank you for a problem report. Please, send the exact version of MySQL server used, 5.0.x.
[18 Nov 2007 20:20]
patrick joos
Hi, Ty for the quick response. Please this is a very urgent problem. We are using the MySQL 5.0.37 version. Tyvm. greetings
[18 Nov 2007 20:23]
patrick joos
Sorry some more additional info, libmySQL.dll newest version.
[19 Nov 2007 5:26]
Valeriy Kravchuk
Please, try to repeat with a newer version, 5.0.45, and inform about the results.
[19 Nov 2007 13:00]
Torsten Blanke
Hallo! The problem is not on serverside. The application work wherry well on XT and win 2000 but not for vista 32/64 bit. The "MySQL Client run out of memory" it's client error and need fix. Wat make the programm? -It's a admin/cheat protection mod for far cry -we use the libmySQL.dll on client side and games server side [b]client:[/b] -The client create a account -- i.O on client and mysql DB - by the first login transfers the client his ID, created by farcry, to the DB and her is the problem. The ID does not transfer to the DB. the client chrash by "MySQL Client run out of memory" and APPCRASH [b]games server[/b] -check, user exist in DB and has a valid ID.. -create a controlle connection to the DB and check client account exist , is banned or not
[20 Nov 2007 10:19]
MySQL Verification Team
Thank you for the feedback. If the issue only happens on Vista could you please provide how to repeat in English and the test case sample. Thanks in advance.
[20 Dec 2007 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".