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

osx test case errors: rpl.rpl_old_master 'innodb,stmt', rpl.rpl_upgrade_master_info 'mix' and rpl.rpl_connection 'mix', main.auth_rpl 'row'

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.2.4
    • 10.2
    • None
    • None
    • osx10.12-x86_64
      AppleClang 8.1.0.8020038

    Description

      https://travis-ci.org/grooverdan/mariadb-server/jobs/218230308#L6674 contains errors in rpl.rpl_old_master 'innodb,stmt', rpl.rpl_upgrade_master_info 'mix' and rpl.rpl_connection 'mix', containing malloc checksum errors.

      2017-04-03 22:24:21 140736652686272 [Note] Server socket created on IP: '127.0.0.1'.
       
      2017-04-03 22:24:21 140736652686272 [Note] Reading of all Master_info entries succeded
       
      2017-04-03 22:24:21 140736652686272 [Note] Added new Master_info '' to hash table
       
      2017-04-03 22:24:21 140736652686272 [Note] /Users/travis/build/grooverdan/mariadb-server/sql/mysqld: ready for connections.
       
      Version: '10.2.5-MariaDB-log'  socket: '/Users/travis/build/grooverdan/mariadb-server/mysql-test/var/tmp/6/mysqld.1.sock'  port: 16080  Source distribution
       
      mysqld(40540,0x70000295f000) malloc: *** error for object 0x7fe049c89ce0: incorrect checksum for freed object - object was probably modified after being freed.
       
      *** set a breakpoint in malloc_error_break to debug
       
      170403 22:24:21 [ERROR] mysqld got signal 6 ;
       
      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.2.5-MariaDB-log
       
      key_buffer_size=1048576
       
      read_buffer_size=131072
       
      max_used_connections=2
       
      max_threads=153
       
      thread_count=9
       
      It is possible that mysqld could use up to 
       
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62976 K  bytes of memory
       
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fe04a0c9408
       
      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...
       
      stack_bottom = 0x70000295ee60 thread_stack 0x49000
       
      2017-04-03 22:29:13 123145345376256 [Warning] Aborted connection 9 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      

      https://travis-ci.org/grooverdan/mariadb-server/jobs/218230310#L7570 main.auth_rpl 'row' (signal 6)

      Attachments

        Issue Links

          Activity

            People

              cvicentiu Vicențiu Ciorbaru
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.