Bug #1186 | mysqld-opt 4.0.14 Assertion failure when using myodbc 3.51 | ||
---|---|---|---|
Submitted: | 3 Sep 2003 1:02 | Modified: | 29 Jan 2004 12:58 |
Reporter: | Jim Michaels | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 3.51 | OS: | Windows (win95b) |
Assigned to: | Heikki Tuuri | CPU Architecture: | Any |
[3 Sep 2003 1:02]
Jim Michaels
[22 Sep 2003 0:56]
MySQL Verification Team
I am changing the assignment from Venu to Heikki, because we had already received the reported behavior with InnoDB when running on Win9x machine. For to isolate the issue with MyODBC please do a simple test starting the server with --skip-innodb and use the MyODBC stuff. Regarding InnoDB I did several tests in the past and the cause was generally machines with a poor hardware resource (RAM memory), small and not fixed swap file type, small free hard drive space. Please verify your resources against the memory values assigned for the InnoDB's variables in my.ini/ my.cnf configuration file.
[29 Jan 2004 12:58]
Heikki Tuuri
Hi! I have not heard this assertion failure from other Windows users. The call should return a nonzero value: http://msdn.microsoft.com/library/default.asp?url=/library/enus/sysinfo/base/closehandle.a... but in this case it does not. Win 95 never was too stable an OS. This might be some operating system bug. This probably has nothing to do with the slow startup on Win 9x, which was fixed in 2002 by reducing InnoDB's event semaphores from 40 000 to 4000. Regards, Heikki