Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-20961

Assertion failed: (uint32) ((scanner->horizon) >> 32) > (uint32) ((scanner->page_addr) >> 32), main.delayed failed in buildbot

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/15655

      10.4 f4ba775914d9d997d3a0116a05d09f1a

      main.delayed                             w1 [ fail ]
              Test ended at 2019-10-30 10:39:30
       
      CURRENT_TEST: main.delayed
       
       
      Server [mysqld.1 - pid: 5672, winpid: 5672, exit: 65280] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2019-10-30 10:39:27 709 [Warning] Aborted connection 709 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      2019-10-30 10:39:27 0 [Note] D:/win32-debug/build/sql//Debug/mysqld.exe (mysqld 10.4.9-MariaDB-debug-log) starting as process 8324 ...
      Assertion failed: (uint32) ((scanner->horizon) >> 32) > (uint32) ((scanner->page_addr) >> 32), file D:\win32-debug\build\src\storage\maria\ma_loghandler.c, line 6905
      191030 10:39:27 [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.4.9-MariaDB-debug-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=0
      max_threads=65537
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3635 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_sigabrt_handler()[my_thr_init.c:485]
      ucrtbase.DLL!raise()
      ucrtbase.DLL!abort()
      ucrtbase.DLL!_get_wpgmptr()
      ucrtbase.DLL!_get_wpgmptr()
      ucrtbase.DLL!_wassert()
      mysqld.exe!translog_get_next_chunk()[ma_loghandler.c:6904]
      mysqld.exe!translog_read_next_record_header()[ma_loghandler.c:7317]
      mysqld.exe!run_redo_phase()[ma_recovery.c:2779]
      mysqld.exe!maria_apply_log()[ma_recovery.c:350]
      mysqld.exe!maria_recovery_from_log()[ma_recovery.c:240]
      mysqld.exe!ha_maria_init()[ha_maria.cc:3610]
      mysqld.exe!ha_initialize_handlerton()[handler.cc:557]
      mysqld.exe!plugin_initialize()[sql_plugin.cc:1438]
      mysqld.exe!plugin_init()[sql_plugin.cc:1720]
      mysqld.exe!init_server_components()[mysqld.cc:5198]
      mysqld.exe!win_main()[mysqld.cc:5721]
      mysqld.exe!mysql_service()[mysqld.cc:5963]
      mysqld.exe!mysqld_main()[mysqld.cc:6155]
      mysqld.exe!main()[main.cc:25]
      mysqld.exe!__scrt_common_main_seh()[exe_common.inl:288]
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlInitializeExceptionChain()
      ntdll.dll!RtlInitializeExceptionChain()
      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.
      Writing a core file at D:\win32-debug\build\mysql-test\var\1\mysqld.1\data\
      Minidump written to D:\win32-debug\build\mysql-test\var\1\mysqld.1\data\mysqld.dmp
      ----------SERVER LOG END-------------
      mysqltest failed but provided no output
      The result from queries just before the failure was:
      < snip >
      drop tables tm, t1, t2;
      #
      # MDEV-9621 INSERT DELAYED fails on insert for tables with many columns
      #
      CREATE TABLE t1 (
      a int,b int,c int,d int,e int,f int,g int,h int,i int,j int,k int,l int,m int,n int,o int,p int,q int,r int,s int,t int,u int,v int,x int,y int,z int
      ) ENGINE=MyISAM;
      INSERT DELAYED INTO t1 (a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,x,y,z)
      values                 (1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1);
      INSERT DELAYED INTO t1 (a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,x,y,z)
      values                 (1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1);
      drop table t1;
      #
      # INSERT DELAYED hangs if table was crashed
      #
      create table t1 (a int, b int) engine=myisam;
      insert into t1 values (1,1);
      SET debug_dbug="d,crash_shutdown";
      shutdown;
      ERROR HY000: Lost connection to MySQL server during query
      

      Attachments

        Activity

          People

            sanja Oleksandr Byelkin
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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