JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

Raccoonwao
This post has NOT been accepted by the mailing list yet.
With 64-bit jvm, the glazedlist is often found crashing the JVM at BoyerMooreCaseInsensitiveTextSearchStrategy.indexOf()

Memory is alright at the event time.  No particular pattern is observed.

Any suggestion for the resolution is highly appreciated.


Here is the dump:



------------------------------------------------------------------------------------------


# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000030dc91e, pid=1424, tid=5164
#
# JRE version: 7.0_06-b24
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.2-b09 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J  ca.odell.glazedlists.impl.filter.BoyerMooreCaseInsensitiveTextSearchStrategy.indexOf(Ljava/lang/String;)I
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x000000000fabb000):  JavaThread "Storage Update Thread" [_thread_in_Java, id=5164, stack(0x00000000158a0000,0x00000000159a0000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x000000098251c5f6

Registers:
RAX=0x0000000000000003, RBX=0x000000078251c5e8, RCX=0x00000000ffffffff, RDX=0x00000007820b1948
RSP=0x000000001599f0c0, RBP=0x00000000ffffffff, RSI=0x0000000000000000, RDI=0x000000078251c5d0
R8 =0x00000000ffffffff, R9 =0x000000000000004e, R10=0x00000000f04a38bd, R11=0x0000000000000000
R12=0x0000000000000000, R13=0x000000077650c380, R14=0x0000000000000100, R15=0x000000000fabb000
RIP=0x00000000030dc91e, EFLAGS=0x0000000000010246

Top of Stack: (sp=0x000000001599f0c0)
0x000000001599f0c0:   00000002ffffffff f04a38baeeca1870
0x000000001599f0d0:   000000078270a2a0 000000077650c368
0x000000001599f0e0:   f041632900000003 0000000000000000
0x000000001599f0f0:   0000000700000003 00000007f0780408
0x000000001599f100:   00000007f00d7720 0000000000000000
0x000000001599f110:   000000001599f178 0000000002676a22
0x000000001599f120:   0000000002676a22 000000077650c368
0x000000001599f130:   000000078270a2a0 000000001599f138
0x000000001599f140:   00000007f3431d00 000000001599f1f0
0x000000001599f150:   00000007f3432e48 00000007f3732968
0x000000001599f160:   00000007f3431e28 000000001599f128
0x000000001599f170:   000000001599f1d0 000000001599f238
0x000000001599f180:   00000000026764f0 000000077650c368
0x000000001599f190:   0000000000000017 000000000000000f
0x000000001599f1a0:   000000078251c5b8 0000000000000000
0x000000001599f1b0:   0000000782532b70 000000078270a2a0

Instructions: (pc=0x00000000030dc91e)
0x00000000030dc8fe:   44 3b 04 24 8b 0c 24 44 0f 4c c1 41 3b e8 7e 10
0x00000000030dc90e:   8b f5 b9 ff ff ff ff 89 4c 24 2c e9 f7 fe ff ff
0x00000000030dc91e:   44 0f b7 5c 6b 10 83 c6 fe 83 fd ff 0f 8e fd 01
0x00000000030dc92e:   00 00 45 3b d9 0f 84 ac 00 00 00 44 0f b7 5c 6f


Register to memory mapping:

RAX=0x0000000000000003 is an unknown value
RBX=0x000000078251c5e8 is an oop
[C
 - klass: {type array char}
 - length: 3
RCX=0x00000000ffffffff is an unknown value
RDX=0x00000007820b1948 is an oop
[I
 - klass: {type array int}
 - length: 256
RSP=0x000000001599f0c0 is pointing into the stack for thread: 0x000000000fabb000
RBP=0x00000000ffffffff is an unknown value
RSI=0x0000000000000000 is an unknown value
RDI=0x000000078251c5d0 is an oop
[C
 - klass: {type array char}
 - length: 3
R8 =0x00000000ffffffff is an unknown value
R9 =0x000000000000004e is an unknown value
R10=0x00000000f04a38bd is an unknown value
R11=0x0000000000000000 is an unknown value
R12=0x0000000000000000 is an unknown value
R13=
[error occurred during error reporting (printing register info), id 0xc0000005]

Stack: [0x00000000158a0000,0x00000000159a0000],  sp=0x000000001599f0c0,  free space=1020k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
J  ca.odell.glazedlists.impl.filter.BoyerMooreCaseInsensitiveTextSearchStrategy.indexOf(Ljava/lang/String;)I




...

Compilation events (10 events):
...
Event: 5089.487 Thread 0x000000000cd1d800 3812             ca.odell.glazedlists.impl.filter.BoyerMooreCaseInsensitiveTextSearchStrategy::indexOf (147 bytes)



Environment Variables:
PATH=C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;c:\Program Files (x86)\Intel\iCLS Client\;c:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\Common Files\Roxio Shared\10.0\DLLShared\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;;C:\Program Files (x86)\NTP\bin
OS=Windows_NT
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 58 Stepping 9, GenuineIntel



---------------  S Y S T E M  ---------------

OS: Windows 7 , 64 bit Build 7601 Service Pack 1

CPU:total 8 (4 cores per cpu, 2 threads per core) family 6 model 58 stepping 9, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, avx, ht, tsc, tscinvbit, tscinv

Memory: 4k page, physical 6233008k(2789500k free), swap 12464164k(8082260k free)

vm_info: Java HotSpot(TM) 64-Bit Server VM (23.2-b09) for windows-amd64 JRE (1.7.0_06-b24), built on Aug  9 2012 20:44:07 by "java_re" with unknown MS VC++:1600

time: Tue Sep 24 09:34:42 2013
elapsed time: 5092 seconds

Reply | Threaded
Open this post in threaded view
|

Re: JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

blakew
This post has NOT been accepted by the mailing list yet.
+1

I am also seeing similar behavior:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000000292d079, pid=8576, tid=8920
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J  ca.odell.glazedlists.impl.filter.TextMatchers.matches(Ljava/util/List;Lca/odell/glazedlists/TextFilterator;[Lca/odell/glazedlists/impl/filter/SearchTerm;[Lca/odell/glazedlists/impl/filter/TextSearchStrategy;Ljava/lang/Object;)Z
#
Reply | Threaded
Open this post in threaded view
|

Re: JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

Raccoonwao
This post has NOT been accepted by the mailing list yet.
Very likely due to the same cause,

TextSearchStrategy.indexOf()
Reply | Threaded
Open this post in threaded view
|

Re: JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

elvison
This post has NOT been accepted by the mailing list yet.
This happened to me as well. The error was either
# J  ca.odell.glazedlists.impl.filter.TextMatchers.matches(Ljava/util/List;Lca/odell/glazedlists/TextFilterator;[Lca/odell/glazedlists/impl/filter/SearchTerm;[Lca/odell/glazedlists/impl/filter/TextSearchStrategy;Ljava/lang/Object;)Z
or
# J  ca.odell.glazedlists.impl.filter.BoyerMooreCaseInsensitiveTextSearchStrategy.indexOf(Ljava/lang/String;)I

They are basically the same action - the second method is called in the first one. I don't have any solid way to reprooduce the problem, as this happens kinda randomly, only in 64-bit environment.

Investigation done so far:
- running with compressed oops OFF: no luck
- compiling source codes myself instead of importing jar library: no luck

Please share with me if you can think of anything we can test. Thanks.
Reply | Threaded
Open this post in threaded view
|

Re: JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

blakew
This post has NOT been accepted by the mailing list yet.
No replies?  How do we get this message in front of the developers?  I've subscribed to the mailing list when I first posted long ago.

This crash is happening all the time...
Reply | Threaded
Open this post in threaded view
|

Re: JVM crash at BoyerMooreCaseInsensitiveTextSearchStrategy

hbrands
Administrator
This post has NOT been accepted by the mailing list yet.
I've not seen this issue myself in our app, yet.
If I'm not mistaken, this issue correspondes with
https://java.net/jira/browse/GLAZEDLISTS-564

My feeling is, that it's most likely a JVM issue.
The first step would be to try to write a test app or test case
that demonstrates this issue.
Since Glazed Lists is an open source project, everyone is invited to contribute.
Then, I would recommend to submit an issue to the Oracle bug database.
But with a test case or test app we might be able to find a workaround in Glazed Lists itself.

Please continue this discussion on the cited issue or on the Glazed Lists user mailing list.
If you post via the nabble forum, please use an account that is registered for the Glazed Lists mailing list,
else the Glazed Lists folks don't get any notice.
There appears to be some nabble issue:
http://support.nabble.com/posting-via-nabble-without-mailing-list-membership-not-working-anymore-td7587636.html

Thanks,
Holger