[jira] [Commented] (LUCENE-8175) ICUTokenizer might return corrupt tokens due to concurrency bug in ICU4J

["Adrien Grand (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364363#comment-16364363 ] 

Adrien Grand commented on LUCENE-8175:
--------------------------------------

For the record, I can reproduce the issue all the time with {{ant beast -Dbeast.iters=100 -Dtestcase=TestICUTokenizer -Dtests.method=testRandomHugeStrings}}.

> ICUTokenizer might return corrupt tokens due to concurrency bug in ICU4J
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-8175
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8175
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Priority: Critical
>
> I was digging some test failures with {{testRandomHugeStrings}} that occurred since the upgrade to ICU4J 60.2 which happen to boil down to this bug: http://bugs.icu-project.org/trac/ticket/13512 which is fixed but not released yet.
> In short an int[] is shared across several threads while it shouldn't. As a consequence, ICUTokenizer may sometimes return corrupt tokens. I pinged on the issue to know when a release fixing this bug is expected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org