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

assertion xid_seqno > trx_sys_cur_xid_seqno

        Details

        • Type: Bug
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: 5.5.37-galera
        • Fix Version/s: None
        • Component/s: None
        • Labels:
        • Environment:
          ubuntu precise x86_64

          Description

          compiled in debug mode (-DCMAKE_BUILD_TYPE=Debug in debian/rules as argument to cmake)

          Jun 20 09:24:29 venus mysqld: 140620  9:24:29  InnoDB: Assertion failure in thread 669300480 in file trx0sys.c line 1005
Jun 20 09:24:29 venus mysqld: InnoDB: Failing assertion: xid_seqno > trx_sys_cur_xid_seqno
Jun 20 09:24:29 venus mysqld: InnoDB: We intentionally generate a memory trap.

            Gliffy Diagrams

              Attachments

              1. my.cnf
                5 kB
              2. syslog
                19 kB
              3. valgrind.mysqld.7706
                392 kB

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                nirbhay_c Nirbhay Choubey added a comment -

                Is it reproducible in normal conditions? My builds are all 'Debug' and I have so far not
                noticed this. Do you have a reproducible test case? I see a similar issue reported here :
                https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1282034

                Show
                nirbhay_c Nirbhay Choubey added a comment - Is it reproducible in normal conditions? My builds are all 'Debug' and I have so far not noticed this. Do you have a reproducible test case? I see a similar issue reported here : https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1282034
                Hide
                Permalink
                nirbhay_c Nirbhay Choubey added a comment -

                I guess the attached valgrind output is linked to MDEV#6300?

                Show
                nirbhay_c Nirbhay Choubey added a comment - I guess the attached valgrind output is linked to MDEV#6300?
                Hide
                Permalink
                danblack Daniel Black added a comment -

                It was reproducible in the scene that the same syslog output occurred on every restart. I reverted to a standard build and am running valgrind to find data for #6300 on this server currently. I can start to looking at this bug after the memleak. If I get a gdb breakpoint at the assert line number if there any particular data structures to print out? Any other early configuration items I can try?

                Though the valgrind output was attempting to find the resolution to #6300 the server didn't really start or get the application interaction to get required to examine the #6300 for that memory leak.

                Show
                danblack Daniel Black added a comment - It was reproducible in the scene that the same syslog output occurred on every restart. I reverted to a standard build and am running valgrind to find data for #6300 on this server currently. I can start to looking at this bug after the memleak. If I get a gdb breakpoint at the assert line number if there any particular data structures to print out? Any other early configuration items I can try? Though the valgrind output was attempting to find the resolution to #6300 the server didn't really start or get the application interaction to get required to examine the #6300 for that memory leak.
                Hide
                Permalink
                danblack Daniel Black added a comment -

                sorry, have been unable to reproduce this.

                Show
                danblack Daniel Black added a comment - sorry, have been unable to reproduce this.

                  People

                  • Assignee:
                    nirbhay_c Nirbhay Choubey
                    Reporter:
                    danblack Daniel Black
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated: