Details

    Description

      Hi, i have this problem

      https://stackoverflow.com/questions/47006605/installing-xampp-on-windows-10-via-bootcamp

      someone telling me to report to this site, and maybe you guys could develop the fix.

      Thanks

      Attachments

        Issue Links

          Activity

            Could you please try to add innodb_flush_method=normal to the config file and see if it helps?

            elenst Elena Stepanova added a comment - Could you please try to add innodb_flush_method=normal to the config file and see if it helps?
            chrishadianto chrishadianto added a comment -

            Hi @Elena Stepanova,
            it still not working

             
            Server version: 10.1.28-MariaDB
            key_buffer_size=16777216
            read_buffer_size=262144
            max_used_connections=0
            max_threads=1001
            thread_count=0
            It is possible that mysqld could use up to 
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787113 K  bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.
             
            Thread pointer: 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...
            mysqld.exe!my_parameter_handler()
            mysqld.exe!strxnmov()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?replace_handler@QUICK_SELECT_I@@UAEXPAVhandler@@@Z()
            mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
            mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
            mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
            mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
            mysqld.exe!?win_main@@YAHHPAPAD@Z()
            mysqld.exe!?mysql_service@@YAHPAX@Z()
            mysqld.exe!strxnmov()
            KERNEL32.DLL!BaseThreadInitThunk()
            ntdll.dll!RtlGetAppContainerNamedObjectPath()
            ntdll.dll!RtlGetAppContainerNamedObjectPath()
            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.
            2017-11-26 13:02:35 d5c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
            2017-11-26 13:02:35 3420 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
             
            2017-11-26 13:02:35 3420 [Note] InnoDB: Using mutexes to ref count buffer pool pages
            2017-11-26 13:02:35 3420 [Note] InnoDB: The InnoDB memory heap is disabled
            2017-11-26 13:02:35 3420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
            2017-11-26 13:02:35 3420 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
            2017-11-26 13:02:35 3420 [Note] InnoDB: Compressed tables use zlib 1.2.3
            2017-11-26 13:02:35 3420 [Note] InnoDB: Using generic crc32 instructions
            2017-11-26 13:02:35 3420 [Note] InnoDB: Initializing buffer pool, size = 16.0M
            2017-11-26 13:02:35 3420 [Note] InnoDB: Completed initialization of buffer pool
            2017-11-26 13:02:35 d5c  InnoDB: Operating system error number 3 in a file operation.
            InnoDB: The error means the system cannot find the path specified.
            InnoDB: If you are installing InnoDB, remember that you must create
            InnoDB: directories yourself, InnoDB does not create them.
             InnoDB: Operation create to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2046
            2017-11-26 13:02:35 3420 [ERROR] InnoDB: File xampp\mysql\data\ibdata1: 'create' returned OS error 203. Cannot continue operation
            171126 13:02:35 [ERROR] mysqld got exception 0x80000003 ;
            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.
             
            To report this bug, see https://mariadb.com/kb/en/reporting-bugs
             
            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.
             
            Server version: 10.1.28-MariaDB
            key_buffer_size=16777216
            read_buffer_size=262144
            max_used_connections=0
            max_threads=1001
            thread_count=0
            It is possible that mysqld could use up to 
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787113 K  bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.
             
            Thread pointer: 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...
            mysqld.exe!my_parameter_handler()
            mysqld.exe!strxnmov()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
            mysqld.exe!?replace_handler@QUICK_SELECT_I@@UAEXPAVhandler@@@Z()
            mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
            mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
            mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
            mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
            mysqld.exe!?win_main@@YAHHPAPAD@Z()
            mysqld.exe!?mysql_service@@YAHPAX@Z()
            mysqld.exe!strxnmov()
            KERNEL32.DLL!BaseThreadInitThunk()
            ntdll.dll!RtlGetAppContainerNamedObjectPath()
            ntdll.dll!RtlGetAppContainerNamedObjectPath()
            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.
            

            chrishadianto chrishadianto added a comment - Hi @Elena Stepanova, it still not working   Server version: 10.1 . 28 -MariaDB key_buffer_size= 16777216 read_buffer_size= 262144 max_used_connections= 0 max_threads= 1001 thread_count= 0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787113 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.   Thread pointer: 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... mysqld.exe!my_parameter_handler() mysqld.exe!strxnmov() mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?replace_handler @QUICK_SELECT_I @ @UAEXPAVhandler @@ @Z () mysqld.exe!?ha_initialize_handlerton@ @YAHPAUst_plugin_int @@ @Z () mysqld.exe!?plugin_init@ @YAHPAHPAPADH @Z () mysqld.exe!?plugin_init@ @YAHPAHPAPADH @Z () mysqld.exe!?init_net_server_extension@ @YAXPAVTHD @@ @Z () mysqld.exe!?win_main@ @YAHHPAPAD @Z () mysqld.exe!?mysql_service@ @YAHPAX @Z () mysqld.exe!strxnmov() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlGetAppContainerNamedObjectPath() ntdll.dll!RtlGetAppContainerNamedObjectPath() 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. 2017 - 11 - 26 13 : 02 : 35 d5c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.   2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: The InnoDB memory heap is disabled 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: Compressed tables use zlib 1.2 . 3 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: Using generic crc32 instructions 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: Initializing buffer pool, size = 16 .0M 2017 - 11 - 26 13 : 02 : 35 3420 [Note] InnoDB: Completed initialization of buffer pool 2017 - 11 - 26 13 : 02 : 35 d5c InnoDB: Operating system error number 3 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. InnoDB: Operation create to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2046 2017 - 11 - 26 13 : 02 : 35 3420 [ERROR] InnoDB: File xampp\mysql\data\ibdata1: 'create' returned OS error 203 . Cannot continue operation 171126 13 : 02 : 35 [ERROR] mysqld got exception 0x80000003 ; 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.   To report this bug, see https: //mariadb.com/kb/en/reporting-bugs   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.   Server version: 10.1 . 28 -MariaDB key_buffer_size= 16777216 read_buffer_size= 262144 max_used_connections= 0 max_threads= 1001 thread_count= 0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787113 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.   Thread pointer: 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... mysqld.exe!my_parameter_handler() mysqld.exe!strxnmov() mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?get_trg_event_map @Update_rows_log_event @ @UAEEXZ () mysqld.exe!?replace_handler @QUICK_SELECT_I @ @UAEXPAVhandler @@ @Z () mysqld.exe!?ha_initialize_handlerton@ @YAHPAUst_plugin_int @@ @Z () mysqld.exe!?plugin_init@ @YAHPAHPAPADH @Z () mysqld.exe!?plugin_init@ @YAHPAHPAPADH @Z () mysqld.exe!?init_net_server_extension@ @YAXPAVTHD @@ @Z () mysqld.exe!?win_main@ @YAHHPAPAD @Z () mysqld.exe!?mysql_service@ @YAHPAX @Z () mysqld.exe!strxnmov() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlGetAppContainerNamedObjectPath() ntdll.dll!RtlGetAppContainerNamedObjectPath() 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.
            chrishadianto chrishadianto added a comment - - edited

            i just notice there's this : "D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2046" , there's no D: drive under bootcamp installation. Where can i change it ?

            I'm using xampp-win32-7.1.10-0-VC14-installer as control panel software

            chrishadianto chrishadianto added a comment - - edited i just notice there's this : "D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2046" , there's no D: drive under bootcamp installation. Where can i change it ? I'm using xampp-win32-7.1.10-0-VC14-installer as control panel software

            This path comes from the build environment, not from yours (that's where the source file was when packages were built).

            elenst Elena Stepanova added a comment - This path comes from the build environment, not from yours (that's where the source file was when packages were built).
            chrishadianto chrishadianto added a comment -

            Just found there're people having this issue also : https://bugs.mysql.com/bug.php?id=85020

            chrishadianto chrishadianto added a comment - Just found there're people having this issue also : https://bugs.mysql.com/bug.php?id=85020

            Fixed with MDEV-16596

            wlad Vladislav Vaintroub added a comment - Fixed with MDEV-16596

            People

              wlad Vladislav Vaintroub
              chrishadianto chrishadianto
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.