Bug #45844 Issues when installing MySQL on Vista
Submitted: 30 Jun 2009 8:30 Modified: 30 Jun 2009 17:47
Reporter: René Loijens Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.1 OS:Microsoft Windows (Vista Home Premium)
Assigned to: CPU Architecture:Any
Tags: innodb, install, mysqld

[30 Jun 2009 8:30] René Loijens
Description:
I try to install MySQL on Vista and I have a sequence of issues related to start the MySQL service when configuring with the wizard: access rights but I manageg by turning off UAC, afterwards wrong size of 24M in the my.ini file for the log file I replaced by 10M (but there is no visiblelog file). I tried to start the service using the console but I never used MySQL before on this computer. Thus, all the innodb directory files are new. Currently I am facing whit new issues. the last one gives the following console trace:
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000; asc
                                                      ;InnoDB: End of page dump
090630  9:51:41  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum
 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
090630  9:51:41InnoDB: Error: trying to access a stray pointer 835C3FF8
InnoDB: buf pool start is at 035B4000, end at 064B4000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: how to force recovery.
090630  9:51:41  InnoDB: Assertion failure in thread 5524 in file G:\mysql-5.1.3
5-winbuild\mysql-community-nt-5.1.35-build\storage\innobase\include\buf0buf.ic l
ine 264
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
090630  9:51:41 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=26214400
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58231 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
006EBA60    mysqld.exe!buf_frame_align()[buf0buf.ic:264]
006D148C    mysqld.exe!page_dir_slot_get_rec()[page0page.ic:503]
0071C216    mysqld.exe!page_cur_search_with_match()[page0cur.c:351]
006D775C    mysqld.exe!btr_cur_search_to_nth_level()[btr0cur.c:520]
00700FE0    mysqld.exe!btr_pcur_open()[btr0pcur.ic:494]
00701CB6    mysqld.exe!btr_pcur_open_on_user_rec()[btr0pcur.c:550]
006F773A    mysqld.exe!dict_load_indexes()[dict0load.c:610]
006F7AA7    mysqld.exe!dict_load_sys_table()[dict0load.c:1015]
0070CED8    mysqld.exe!dict_boot()[dict0boot.c:389]
006BFEBA    mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1521]
006AE2F3    mysqld.exe!innobase_init()[ha_innodb.cc:1755]
00442BB8    mysqld.exe!ha_initialize_handlerton()[handler.cc:432]
00565403    mysqld.exe!plugin_initialize()[sql_plugin.cc:1003]
00569D44    mysqld.exe!plugin_init()[sql_plugin.cc:1216]
004D0CFB    mysqld.exe!init_server_components()[mysqld.cc:3884]
004D1436    mysqld.exe!win_main()[mysqld.cc:4354]
004D188D    mysqld.exe!mysql_service()[mysqld.cc:4530]
004D1B30    mysqld.exe!main()[mysqld.cc:4703]
0072BA9D    mysqld.exe!__tmainCRTStartup()[crt0.c:327]
01501973
2D00646C
6E6F632D
656C6F73
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
To try a first installation of MySQL on Windows Vista on a account with Admistrator rights
Use all default parameter of the install wizard
The configuration wizard is unable to start the service
Using msqld --console to start on the MS Dos console gives an access right error 
Turn off UAC on Vista
Using msqld --console to start on the MS Dos console gives the above error and trace
[30 Jun 2009 17:47] MySQL Verification Team
Thank you for the bug report. Duplicate of bug: http://bugs.mysql.com/bug.php?id=44416.