Bug 2050922 - Coredump of Java8 UML application only on wayland
Summary: Coredump of Java8 UML application only on wayland
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.8.0-openjdk
Version: 35
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-05 00:17 UTC by GroovieMan
Modified: 2022-02-11 08:07 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-02-11 07:07:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log file from Magicdraw (182.94 KB, text/plain)
2022-02-05 00:17 UTC, GroovieMan
no flags Details

Description GroovieMan 2022-02-05 00:17:56 UTC
Created attachment 1859170 [details]
Log file from Magicdraw

Description of problem:
Running my UML Editor (MagicDraw) using Java8 (is a must) on a brand new F35 cause a SEGV each time i peroform the same operation.

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f9b8dc158e1, pid=22644, tid=0x00007f9b874d2640
#
# JRE version: Java(TM) SE Runtime Environment (8.0_321-b07) (build 1.8.0_321-b07)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.321-b07 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libawt_xawt.so+0x468e1]  ReadRegionsInList.constprop.5+0x671
#
# Core dump written. Default location: /home/cgroove/localApps/MagicDraw/core or core.22644
#
# 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.



Version-Release number of selected component (if applicable):
java-1.8.0-openjdk-headless-1.8.0.312.b07-2.fc35.x86_64

How reproducible:
The crash occurs constanly at the same place(s) only on my Wayland Desktop (F35 with Wayland Gnome). Simple create a new artifact and the app crashed.


Steps to Reproduce:
1.create a new artifact (a disgram) the it crashes
2.
3.

Actual results:
a crash

Expected results:
no crash

Additional info:
please not, the is an older bug entry 1402819.

Comment 1 GroovieMan 2022-02-07 17:13:15 UTC
Instead of openjdk i also gave sun/oracle Java8 jdk a try and had the same problem.
Maybe the X11 access to wayland may have a problem too.

Comment 2 GroovieMan 2022-02-11 07:05:51 UTC
Salut 

Today i received a jdk8 update with java-1.8.0-openjdk-1.8.0.322.b06-2.fc35.x86_64 and the problem disappeard!
Thank you for your great job!

Christian

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

Those Magnificent Men in their Flying Machines!

Comment 3 GroovieMan 2022-02-11 08:07:52 UTC
Postmark: 

The crash disappeard but all X11 application do not allow windows operations so there is a X11 protocol issue too!


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