[
https://java.net/jira/browse/GLAZEDLISTS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=383711#comment-383711 ]
brands commented on GLAZEDLISTS-564:
------------------------------------
This issue was not fixed in the latest Java CPU releases.
I've build a new snapshot release of Glazed Lists available in the Java.net Snapshot repo:
https://maven.java.net/content/repositories/snapshots/net/java/dev/glazedlists/glazedlists_java15/1.9.1-SNAPSHOT/groupId: net.java.dev.glazedlists
artifactId: glazedlists_java16
version: 1.9.1-SNAPSHOT
it contains the workaround suggested here:
https://github.com/glazedlists/glazedlists/pull/3Please let me know, if it works for you. We'll then go on and release official 1.9.1 version.
> SIGSEGV in TextMatchers.matches
> -------------------------------
>
> Key: GLAZEDLISTS-564
> URL:
https://java.net/jira/browse/GLAZEDLISTS-564> Project: glazedlists
> Issue Type: Bug
> Affects Versions: 1.8.0
> Environment: Fedora 18
> JRE version: 7.0_21-b11
> Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops)
> Reporter: cmadsen_dk
>
> Using Java 7 64 bit I get a SIGSEGV in TextMatchers.matches when I'm
> trying to filter a list (through a JTextField) that is being updated by
> another thread.
> The log file looks like this:
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f936589546d, pid=6793,
> tid=140269955303168
> #
> # JRE version: 7.0_21-b11
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # J
> ca.odell.glazedlists.impl.filter.TextMatchers.matches(Ljava/util/List;L
> ca/odell/glazedlists/TextFilterator;[Lca/odell/glazedlists/impl/filter/
> SearchTerm;[Lca/odell/glazedlists/impl/filter/TextSearchStrategy;Ljava/
> lang/Object;)Z
> #
> # Failed to write core dump. Core dumps have been disabled. To enable
> core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # hs_err_pid6793.log
> Any hints on how to solve this?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)