[JIRA] (GLAZEDLISTS-564) SIGSEGV in TextMatchers.matches

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (GLAZEDLISTS-564) SIGSEGV in TextMatchers.matches

JIRA jira-no-reply@java.net

    [ https://java.net/jira/browse/GLAZEDLISTS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=383713#comment-383713 ]

cryowizard commented on GLAZEDLISTS-564:
----------------------------------------

AFAIK, the fix will not be included in a CPU. We were told the quarterly March/April update.

The bugs are marked as FIXED in Oracle's bug DB for both 7 and 8.

7u80 and 8u40 are not out yet, officially anyway.

> 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)