Bug #63933 CREATE FULLTEXT INDEX causes crahs
Submitted: 5 Jan 2012 12:41 Modified: 23 Mar 2012 18:47
Reporter: Alex W Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: FULLTEXT search Severity:S2 (Serious)
Version:5.6.4 M7 OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[5 Jan 2012 12:41] Alex W
Description:
Running this causes MySQL to crash.

CREATE FULLTEXT INDEX FT_Search ON tbl_options (`value`);

Table is INNODB, The `value` column is a LONGTEXT type.

Dump from log -

120105 12:23:57 InnoDB: Rebuild table mydb@0020v2/tbl_options to add DOC_ID column
Unrecognized character: 40
120105 12:23:57  InnoDB: Assertion failure in thread 5144 in file pars0lex.l line 686
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.
120105 12:23:57 - mysqld got exception 0xc0000005 ;
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.

key_buffer_size=57671680
read_buffer_size=65536
max_used_connections=1
max_threads=100
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 89419 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xe24c370
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...
00000001401C4110    mysqld.exe!radixsort_for_str_ptr()
00000001401E5BC2    mysqld.exe!radixsort_for_str_ptr()
00000001401A8B66    mysqld.exe!radixsort_for_str_ptr()
00000001401A1ACE    mysqld.exe!radixsort_for_str_ptr()
00000001400B7FDF    mysqld.exe!radixsort_for_str_ptr()
0000000140135541    mysqld.exe!radixsort_for_str_ptr()
000000013FEEC71B    mysqld.exe!?mysql_alter_table@@YA_NPEAVTHD@@PEAD1PEAUst_ha_create_information@@PEAUTABLE_LIST@@PEAVAlter_info@@IPEAUst_order@@_N@Z()
000000013FE322EB    mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@@Z()
000000013FE35C69    mysqld.exe!?mysql_parse@@YAXPEAVTHD@@PEADIPEAVParser_state@@@Z()
000000013FE36AEF    mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PEAVTHD@@PEADI@Z()
000000013FE37E27    mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
000000013FE98F27    mysqld.exe!?do_handle_one_connection@@YAXPEAVTHD@@@Z()
000000013FE98FDA    mysqld.exe!handle_one_connection()
000000014006B0EE    mysqld.exe!win_pthread_mutex_trylock()
00000001402CA617    mysqld.exe!my_mb_ctype_mb()
InnoDB: Thread 5156 stopped in file ut0ut.cc line 80
00000001402CA6CB    mysqld.exe!my_mb_ctype_mb()
000000007708652D    kernel32.dll!BaseThreadInitThunk()
000000007741C521    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (000000000E313810): CREATE FULLTEXT INDEX FT_Search ON tbl_options (`value`)
Connection ID (thread ID): 2
Status: NOT_KILLED

How to repeat:
Try to create a FULLTEXT index on a column in an innoDB table.
[5 Jan 2012 12:56] MySQL Verification Team
Please provide the complete create table statement and your my.ini file (I couldn't repeat on my own table). Thanks.
[6 Feb 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[23 Mar 2012 18:47] MySQL Verification Team
Duplicate of bug http://bugs.mysql.com/bug.php?id=64745 which has a test case.