Comment 3 for bug 1255027

It crushes with mysqldump:

mysqldump abover "log:2013-10-29:pages" > file

CREATE TABLE `log:2013-10-29:pages` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `user_id` bigint(20) unsigned NOT NULL,
  `useragent_id` bigint(20) unsigned NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `ip` bigint(20) unsigned NOT NULL DEFAULT '0',
  `page` varchar(2048) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `ads` (`user_id`,`time`),
  KEY `time` (`time`),
  KEY `page` (`page`(255))
) ENGINE=InnoDB AUTO_INCREMENT=120285953102 DEFAULT CHARSET=utf8

explain select count(*) from `log:2013-10-29:pages`\G
*************************** 1. row ***************************
           id: 1
  select_type: SIMPLE
        table: log:2013-10-29:pages
         type: index
possible_keys: NULL
          key: time
      key_len: 4
          ref: NULL
         rows: 11962960
        Extra: Using index
1 row in set (0.00 sec)

2013-12-06 13:46:30 7efad6a54700 InnoDB: Assertion failure in thread 139615808079616 in file btr0pcur.cc line 452
InnoDB: Failing assertion: page_is_comp(next_page) == page_is_comp(page)
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:46:30 UTC - 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.
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=73
max_threads=130
thread_count=9
connection_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 84554 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7efab41d77b0
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 = 7efad6a53e30 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8cc57e]
/usr/sbin/mysqld(handle_fatal_signal+0x4a1)[0x69d6a1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7f020e35f030]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f020c9d1475]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f020c9d46f0]
/usr/sbin/mysqld[0xa87122]
/usr/sbin/mysqld[0xa20875]
/usr/sbin/mysqld[0xa2423b]
/usr/sbin/mysqld[0x97bd50]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x66)[0x600406]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1c)[0x81ae5c]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x181)[0x6f0be1]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x2b8)[0x6effd8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x265)[0x72ea75]
/usr/sbin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x16d)[0x72ed1d]
/usr/sbin/mysqld[0x5caf33]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1fc4)[0x70ecf4]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5b8)[0x711e48]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xf52)[0x712e22]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x15f)[0x6e831f]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6e8407]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0x963d93]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f020e356b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f020ca79a7d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (313db890): SELECT /*!40001 SQL_NO_CACHE */ * FROM `log:2013-10-29:pages`
Connection ID (thread ID): 47969872
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
131206 13:46:32 mysqld_safe Number of processes running now: 0
131206 13:46:32 mysqld_safe mysqld restarted