Manticore crash when calling call snippets() with libstemmer_fr and index_exact_words #910
Labels
Comments
|
could you provide searchd.log to check the BT from the crash log matched to crash you reported? |
|
My searchd.log with --logdebugvv |
What's next? |
|
Nothing, it's the end of the file. |
MRERun the following one-liner up to 5 times until it crashes: mysql> drop table if exists t; create table t(f text) morphology='libstemmer_fr' index_exact_words='1'; CALL SNIPPETS(('test text 1','test text 2'), 't', 'php developer');
--------------
drop table if exists t
--------------
Query OK, 0 rows affected (0.00 sec)
--------------
create table t(f text) morphology='libstemmer_fr' index_exact_words='1'
--------------
Query OK, 0 rows affected (0.01 sec)
--------------
CALL SNIPPETS(('test text 1','test text 2'), 't', 'php developer')
--------------
ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
ERROR 2003 (HY000): Can't connect to MySQL server on '0:9306' (61)
ERROR:
Can't connect to the serverNotes
|
sanikolaev
changed the title
|
The log result is below. I note that the same problem with morphology='libstemmer_tr' |
|
Fixed in 2b88781 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Manticore crashes when calling call snippets in RT index if morphology is libstemmer_fr and passed an array of more than one text
To Reproduce
Steps to reproduce the behavior:
My example:
My example:
CALL SNIPPETS(('test php text 1','test php text 2', 'test php text 3'), 'fr_index', 'php developer');Describe the environment:
Manticore Search from Docker container manticoresearch/manticore:5.0.2
Messages from log files:
The log is either missing or an error is thrown:
realloc(): invalid old size
Crash!!! Handling signal 11
Crash!!! Handling signal 6
Additional context
After a complete reindexing, the problem remains.
If morphology = libstemmer_fr is replaced by morphology = lemmatize_en, then the problem is solved
The text was updated successfully, but these errors were encountered: