[
https://issues.apache.org/jira/browse/LUCENE-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071555#comment-13071555
]
Robert Muir commented on LUCENE-3335:
-------------------------------------
{quote}
Even if we found a work around for all the affected issues in Lucene that
didn't hurt performance in older JVMs, and spun up a 3.3.1 RC in the next 5
minutes, we still don't have enough time to vote for that release and get it
out to the mirrors by the time Java 7 comes out – let alone have any confidence
that all our users will upgrade Lucene/Solr before they upgrade their JVM.
{quote}
I agree, I'm not implying we should rush anything. But I guess I'm saying its
worth it to understand the scope of what's affected, because if its just:
* PorterStemmer jrecrash <- workarounds already posted here
* Pulsing negative readVint <-- no workaround yet.
well, thats manageable, only one of these affects any released code.
> jrebug causes porter stemmer to sigsegv
> ---------------------------------------
>
> Key: LUCENE-3335
> URL: https://issues.apache.org/jira/browse/LUCENE-3335
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Robert Muir
> Labels: Java7
> Attachments: LUCENE-3335.patch, LUCENE-3335_slow.patch,
> patch-0uwe.patch
>
>
> happens easily on java7: ant test -Dtestcase=TestPorterStemFilter
> -Dtests.iter=100
> might happen on 1.6.0_u26 too, a user reported something that looks like the
> same bug already:
> http://www.lucidimagination.com/search/document/3beaa082c4d2fdd4/porterstemfilter_kills_jvm
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
