Hi! I believe the following patch fixes the startup problems on Win 95/98/ME in InnoDB versions which have been released after July 2, 2002.
Looks like Win XP can easily create 40 000 event semaphores, but for 95/98/ME it is too much. This should be in upcoming MySQL-3.23.53 and MySQL-4.0.5. Thank you for the bug reports. Heikki Innobase Oy ChangeSet 1.1204 02/10/03 18:10:34 [EMAIL PROTECTED] +1 -0 os0thread.h: Fix the probable reason why InnoDB versions after July 2, 2002 did not start properly in some Win 95/98/ME computers innobase/include/os0thread.h 1.7 02/10/03 18:10:26 [EMAIL PROTECTED] +9 -0 Fix the probable reason why InnoDB versions after July 2, 2002 did not start properly in some Win 95/98/ME computers # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: heikki # Host: hundin.mysql.fi # Root: /home/heikki/mysql --- 1.6/innobase/include/os0thread.h Tue Aug 13 01:18:15 2002 +++ 1.7/innobase/include/os0thread.h Thu Oct 3 18:10:26 2002 @@ -15,7 +15,16 @@ /* Maximum number of threads which can be created in the program; this is also the size of the wait slot array for MySQL threads which can wait inside InnoDB */ +#ifdef __WIN__ +/* Windows 95/98/ME seemed to have difficulties creating the all +the event semaphores for the wait array slots. If the computer had +<= 64 MB memory, InnoDB startup could take minutes or even crash. +That is why we set this to only 1000 in Windows. */ + +#define OS_THREAD_MAX_N 1000 +#else #define OS_THREAD_MAX_N 10000 +#endif /* Possible fixed priorities for threads */ #define OS_THREAD_PRIORITY_NONE 100 ----- Original Message ----- From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: "Gelu Gogancea" <[EMAIL PROTECTED]>; "Puiu Hrenciuc" <[EMAIL PROTECTED]>; "Philip Molter" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, October 03, 2002 6:07 PM Subject: Re: MySQL/InnoDB-4.0.4 is released > Gelu, > > ----- Original Message ----- > From: "Gelu Gogancea" <[EMAIL PROTECTED]> > To: "Puiu Hrenciuc" <[EMAIL PROTECTED]>; "Heikki Tuuri" > <[EMAIL PROTECTED]>; "Philip Molter" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Thursday, October 03, 2002 2:40 PM > Subject: Re: MySQL/InnoDB-4.0.4 is released > > > > Hi, > > You have right, in the new version (4.0.4) on Windows 9x are the same > > symptom. > > I research a little in this morning and i found where is the problem when > > the innodb is initialised. > > The problems is in the function: > > sync_array_create() > > ...when it must initialise a lot of "cells"(n_cells=aprox. 6.000.000). > > that number is strange. It should be 10 000. Maybe you have compiled with > optimizations so that the debugger shows a wrong number. > > But this reveals a possible reason for the slowness and other problems in > Win 95/98/ME. > > Can you try the following: in > > \mysql\innobase\include\os0thread.h > > change > > #define OS_THREAD_MAX_N 10000 > > to a smaller value, for example, 100. > > It may be that Win 95/98/ME has problems in creating a large number of event > semaphores. > > You have to recompile the 'innobase' project because the change is in a > header. > > Please report if this helps. > > Regards, > > Heikki > Innobase Oy > > sql query > > > > > The routine is next : > > > > for (i = 0; i < n_cells; i++) { > > cell = sync_array_get_nth_cell(arr, i); > > cell->wait_object = NULL; > > > > /* Create an operating system event semaphore with no name > > */ > > cell->event = os_event_create(NULL); > > cell->event_set = FALSE; /* it is created in reset state */ > > } > > > > The configuration of my computer for testing is: > > CPU : INTEL P IV/1,7 Ghz > > RAM: 512 MB DDRAM > > HDD: 2x40 GB(IDE) > > OS:Windows 98 OSR2 > > > > Maybe this help on Heikki to see what happend. > > > > Regards, > > > > Gelu > > _____________________________________________________ > > G.NET SOFTWARE COMPANY > > > > Permanent e-mail address : [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > ----- Original Message ----- > > From: "Puiu Hrenciuc" <[EMAIL PROTECTED]> > > To: "Heikki Tuuri" <[EMAIL PROTECTED]>; "Philip Molter" > > <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Thursday, October 03, 2002 12:46 AM > > Subject: Re: MySQL/InnoDB-4.0.4 is released > > > > > > > I hoped that you will solve the MySQL consuming all computer's > > > resources in 4.0.4, but nope, the problem is still there. I'm trying > > > to run MySQL on Win ME and when started normally it consumes > > > all resources of my computer. When I start it with --skip-innodb > > > it works just fine. Why ? > > > At least I saw you fixed WinMySQLAdmin. > > > > > > > > > ----- Original Message ----- > > > From: "Heikki Tuuri" <[EMAIL PROTECTED]> > > > To: "Philip Molter" <[EMAIL PROTECTED]> > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > > Sent: Wednesday, October 02, 2002 5:48 PM > > > Subject: Re: MySQL/InnoDB-4.0.4 is released > > > > > > > > > > Philip, > > > > > > > > ----- Original Message ----- > > > > From: "Philip Molter" <[EMAIL PROTECTED]> > > > > To: "Heikki Tuuri" <[EMAIL PROTECTED]> > > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > > > Sent: Wednesday, October 02, 2002 4:16 PM > > > > Subject: Re: MySQL/InnoDB-4.0.4 is released > > > > > > > > > > > > > On Wed, Oct 02, 2002 at 02:12:23PM +0300, Heikki Tuuri wrote: > > > > > : Hi! > > > > > : > > > > > : InnoDB is a table type which provides transactions, row level > > locking, > > > > > : foreign key constraints, and a non-free hot backup tool to MySQL. > > > > > : > > > > > : InnoDB is included in both downloadable versions of MySQL-4.0: > > > MySQL-Pro > > > > and > > > > > : MySQL-Max. > > > > > : > > > > > : Release 4.0.4-beta is mainly a bug fix release. > > > > > > > > > > Will the bugfixes for this release (not necessarily the new/updated > > > > > features) be backported to the 3.23.x series? Given that MySQL 4 > > > > > isn't marked as stable yet, many of us using InnoDB no doubt still > > > > > use 3.23.x. > > > > > > > > of course, the fix will be backported if the bug also existed in 3.23. > > > > > > > > The DESC bugs in 4.0.x are not present in 3.23. > > > > > > > > Since 4.0.x releases will come in more rapid succession than 3.23 > > > releases, > > > > it may soon be that the most bug-free InnoDB is actually in the latest > > > > 4.0.x. > > > > > > > > > * Philip Molter > > > > > * Texas.net Internet > > > > > * http://www.texas.net/ > > > > > * [EMAIL PROTECTED] > > > > > > > > Regards, > > > > > > > > Heikki > > > > Innobase Oy > > > > > > > > sql query > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" > > before > > > > posting. To request this thread, e-mail > [EMAIL PROTECTED] > > > > > > > > To unsubscribe, send a message to the address shown in the > > > > List-Unsubscribe header of this message. If you cannot see it, > > > > e-mail [EMAIL PROTECTED] instead. > > > > > > > > > > > > > --------------------------------------------------------------------- > > > Before posting, please check: > > > http://www.mysql.com/manual.php (the manual) > > > http://lists.mysql.com/ (the list archive) > > > > > > To request this thread, e-mail <[EMAIL PROTECTED]> > > > To unsubscribe, e-mail > <[EMAIL PROTECTED]> > > > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > > > > > > > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php