Bug 1416173 - Crash in libfreeblpriv3.so
Summary: Crash in libfreeblpriv3.so
Keywords:
Status: CLOSED DUPLICATE of bug 1415137
Alias: None
Product: Fedora
Classification: Fedora
Component: nss-softokn
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kai Engert (:kaie) (inactive account)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-24 18:48 UTC by Piergiorgio Sartor
Modified: 2017-01-29 15:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-29 15:11:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Piergiorgio Sartor 2017-01-24 18:48:22 UTC
Description of problem:
I'm seeing a strange crash in a Java software. It reports in happened in libfreeblpriv3.so, which belongs to nss-softokn-freebl which, I assume, belongs to nss-softokn.

Version-Release number of selected component (if applicable):
nss-softokn-freebl-3.28.1-1.0.fc25.x86_64

How reproducible:
It seems systematically happening after upgrade to 3.28.1, while it never happened with 3.27.0 (so, there should be a difference there).

Steps to Reproduce:
1.
Start software with nss-softokn-freebl-3.28.1

Actual results:
It crashes after few seconds, try to restart, crashes again until it gives up with:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fbbc3d9d77b, pid=959, tid=0x00007fbbc3073700
#
# JRE version: OpenJDK Runtime Environment (8.0_111-b16) (build 1.8.0_111-b16)
# Java VM: OpenJDK 64-Bit Server VM (25.111-b16 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libfreeblpriv3.so+0x2077b]


Expected results:
Should run smoothly, as before.

Additional info:
As mentioned above, version 3.27.0 was fine, 3.28.1 has this problem.

If there is anything to test I might give it a try (please tell me how to safely revert, in case).

Thanks,

bye,

pg

Comment 1 Piergiorgio Sartor 2017-01-29 15:11:43 UTC
Uhm, this seems somehow duplicate of #1415137, maybe it can be marked accordingly.

bye,

pg

*** This bug has been marked as a duplicate of bug 1415137 ***


Note You need to log in before you can comment on or make changes to this bug.