Bug #75478 Mysql server crashes while executing innodb full text search with proximity
Submitted: 12 Jan 2015 7:36 Modified: 12 Jan 2015 8:48
Reporter: Mani Rao Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: FULLTEXT search Severity:S1 (Critical)
Version:5.6.10 OS:Microsoft Windows (2008 server R2)
Assigned to: CPU Architecture:Any

[12 Jan 2015 7:36] Mani Rao
Description:
while I am using innodb fulltext search with proximity 100.

for ex:

select count(*) from  ftssearch     WHERE MATCH(XML) AGAINST ('"the tough part"@100' IN BOOLEAN MODE)  

in XML column "the" repeats 200 times. at that case if i execute above query
server has crashed. 

please look into this.

How to repeat:
2015-01-12 00:03:29 3168 [Note] Plugin 'FEDERATED' is disabled.
2015-01-12 00:03:29 3168 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2015-01-12 00:03:29 3168 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-12 00:03:29 3168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-12 00:03:29 3168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-12 00:03:29 3168 [Note] InnoDB: CPU does not support crc32 instructions
2015-01-12 00:03:29 3168 [Note] InnoDB: Initializing buffer pool, size = 10.0G
2015-01-12 00:03:29 3168 [Note] InnoDB: Completed initialization of buffer pool
2015-01-12 00:03:30 3168 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-12 00:03:30 3168 [Note] InnoDB: The log sequence numbers 785459316886 and 785459316886 in ibdata files do not match the log sequence number 796278698265 in the ib_logfiles!
2015-01-12 00:03:30 3168 [Note] InnoDB: Database was not shutdown normally!
2015-01-12 00:03:30 3168 [Note] InnoDB: Starting crash recovery.
2015-01-12 00:03:30 3168 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-12 00:03:30 3168 [Note] InnoDB: Restoring possible half-written data pages 
2015-01-12 00:03:30 3168 [Note] InnoDB: from the doublewrite buffer...
2015-01-12 00:03:32 3168 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-12 00:03:32 3168 [Note] InnoDB: Waiting for purge to start
2015-01-12 00:03:32 3168 [Note] InnoDB: 1.2.10 started; log sequence number 796278698265
2015-01-12 00:03:32 3168 [Note] Server hostname (bind-address): '*'; port: 3306
2015-01-12 00:03:32 3168 [Note] IPv6 is available.
2015-01-12 00:03:32 3168 [Note]   - '::' resolves to '::';
2015-01-12 00:03:32 3168 [Note] Server socket created on IP: '::'.
2015-01-12 00:03:32 3168 [Note] Event Scheduler: Loaded 0 events
2015-01-12 00:03:32 3168 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: ready for connections.
Version: '5.6.10-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
2015-01-12 00:10:44 e20 InnoDB: FTS Optimize Removing table ripmelib_june2014/ftssearch
[12 Jan 2015 8:48] Umesh Shastry
Hello Mani Rao,

Thank you for the report.
I couldn't repeat with latest 5.6.22 GA build with sample data.
Also, version 5.6.10 is very old and many bugs were fixed since. Please upgrade to current version 5.6.22, try with it and inform us if problem
still exists. If you can provide more information(exact repeatable test case - table, and sample data which triggers issue), feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Thanks,
Umesh