LibRxtx-java crash on 64bit

Bug #894718 reported by JVApen on 2011-11-25
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
RXTX
New
Undecided
Unassigned
openjdk-7 (Ubuntu)
Undecided
Unassigned

Bug Description

The usage of the librxtx-pacakge in the openjdk-7 enviorment isn't possible do crashes

JVApen (vanantwerpenjeroen) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openjdk-7 (Ubuntu):
status: New → Confirmed
Xerxes Rånby (xranby) wrote :

Is the sourcecode to the saGroStat.com powerManager available?

This bug is found in the librxtx-java jni code.
It would be great with a simple testcase that demonstrate how to trigger this bug using librxtx-java

# Problematic frame:
# C [librxtxSerial.so+0x75da] Java_gnu_io_RXTXPort_nativeDrain+0xea

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j gnu.io.RXTXPort.nativeDrain(Z)Z+0
j gnu.io.RXTXPort$SerialOutputStream.flush()V+92
j saGroStat.com.power.powerManager.writeData([BII)Z+204
j saGroStat.com.power.powerManager.writeData([B)Z+5
j saGroStat.com.power.powerManager.executeCommand(IIII)Z+122
j saGroStat.com.power.powerManager.executeCommand(III)Z+5
j saGroStat.com.power.powerManager.executeCommand(II)Z+4
j saGroStat.com.power.powerManager.executeCommand(I)Z+3
j saGroStat.com.power.powerManager.reset()Z+3
j saGroStat.com.power.powerManager.main([Ljava/lang/String;)V+39
v ~StubRoutines::call_stub

Xerxes Rånby (xranby) wrote :

Can you trigger the same bug using OpenJDK 6 as well?

Morty (morty) wrote :

I can confirm the problem with sun-java-6 and open-jdk-6

Paul Munday (paulm-4) wrote :

I'm getting the same crash with an unrelated add. The command part of the crash report is this:
# Problematic frame:
# C [librxtxSerial.so+0x7733] Java_gnu_io_RXTXPort_nativeDrain+0xc3

j gnu.io.RXTXPort.nativeDrain(Z)Z+0
j gnu.io.RXTXPort$SerialOutputStream.flush()V+72

Immediately below it I get this:

j com.openbravo.pos.printer.escpos.PrinterWritterRXTX.internalFlush()V+11

the source code for that has this:

    protected void internalFlush() {
        try {
            if (m_out != null) {
                m_out.flush();
            }
        } catch (IOException e) {
            System.err.println(e);
        }
    }

i.e. its crashing trying to flush the serial port I think.

compare to this bug upstream:

http://bugzilla.qbang.org/show_bug.cgi?id=105 (which appears to be the same bug)
and this now closed bug
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/594569

Tiago Stürmer Daitx (tdaitx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:

apport-collect 894718

and any other logs that are relevant for this particular issue.

Changed in openjdk-7 (Ubuntu):
status: Confirmed → Incomplete
Sotiris Lyras (cyberrobots) wrote :

Hello are there any updates regarding the use of RXTXcomm Java's library for ubuntu x64 ? After installing the library my program fails with the following output:

226
h="org.eclipse.jdt.launching.JRE_CONTAINER"/>
 <classpathentry kind="output" path="bin"/>
</classpath>

264
32531
eb 23 17:02:00 2016
elapsed time: 0 seconds (0d 0h 0m 0s)

265
32606
0h 0m 0s)

265
32615
onds (0d 0h 0m 1s)

2
367
ldCommand>
 </buildSpec>
 <natures>
  <nature>org.eclipse.jdt.core.javanature</nature>
 </natures>
</projectDescription>

264
32554
t 4.3.0-8)

time: Tue Feb 23 17:11:51 2016
elapsed time: 0 seconds (0d 0h 0m 0s)

I am at stateIDLE and previous state was IDLE
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f4857df8462, pid=6458, tid=139948683200256
#
# JRE version: Java(TM) SE Runtime Environment (8.0_72-b15) (build 1.8.0_72-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.72-b15 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [librxtxSerial.so+0x6462] read_byte_array+0x52
#
# 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:
# /home/slyras/oldworkspace/newLocal/hs_err_pid6458.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Experimental: JNI_OnLoad called.

Ubuntu 14.04 kde 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Apologies for my delay in responding. I don't have a system where I can
try this to see if it is still an issue.

Best regards,
Tim Sharples

master-ksc (master-ksc) wrote :

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f83aa558d9d, pid=21887, tid=0x00007f83aa316700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_171-b11) (build 1.8.0_171-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.171-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [librxtxSerial.so+0x6d9d] read_byte_array+0x3d
#
# 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:
# /root/Workspaces/MyEclipse 2017/telegram/hs_err_pid21887.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

so See what happened to me,help me please

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.