[
https://issues.apache.org/jira/browse/LUCENE-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071575#comment-13071575
]
Uwe Schindler edited comment on LUCENE-3335 at 7/27/11 7:20 AM:
----------------------------------------------------------------
I verified the above:
{noformat}
modules\analysis\common>ant test -Dargs="-XX:+OptimizeStringConcat"
-Dtestcase=TestPorterStemFilter -Dtests.iter=100
modules\analysis\common>ant test -Dargs="-XX:+AggressiveOpts"
-Dtestcase=TestPorterStemFilter -Dtests.iter=100
{noformat}
Both crash with the same error:
{noformat}
Testsuite: org.apache.lucene.analysis.en.TestPorterStemFilter
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000022171e9, pid=8816,
tid=10952
#
# JRE version: 6.0_24-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64
compressed oops)
# Problematic frame:
# J org.apache.lucene.analysis.en.PorterStemmer.stem(I)Z
#
# An error report file with more information is saved as:
# C:\Users\Uwe
Schindler\Projects\lucene\trunk-lusolr1\modules\analysis\build\common\test\1\hs_err_pid8816.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Test org.apache.lucene.analysis.en.TestPorterStemFilter FAILED (crashed)
{noformat}
This may explain Bernd Fehlings problems, as Solr users often use strange JVM
options because they want to get all speed out of their system (because solr is
slower than native Lucene code...).
was (Author: thetaphi):
I verified the above:
{noformat}
modules\analysis\common>ant test -Dargs="-XX:+OptimizeStringConcat -Xbatch"
-Dtestcase=TestPorterStemFilter -Dtests.iter=100
modules\analysis\common>ant test -Dargs="-XX:+AggressiveOpts"
-Dtestcase=TestPorterStemFilter -Dtests.iter=100
{noformat}
Both crash with the same error:
{noformat}
Testsuite: org.apache.lucene.analysis.en.TestPorterStemFilter
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000022171e9, pid=8816,
tid=10952
#
# JRE version: 6.0_24-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64
compressed oops)
# Problematic frame:
# J org.apache.lucene.analysis.en.PorterStemmer.stem(I)Z
#
# An error report file with more information is saved as:
# C:\Users\Uwe
Schindler\Projects\lucene\trunk-lusolr1\modules\analysis\build\common\test\1\hs_err_pid8816.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Test org.apache.lucene.analysis.en.TestPorterStemFilter FAILED (crashed)
{noformat}
This may explain Bernd Fehlings problems, as Solr users often use strange JVM
options because they want to get all speed out of their system (because solr is
slower than native Lucene 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
