Bug 573208 - Crash in C [libswt-pi3-gtk-4944r20.so+0x4dfb4] Java_org_eclipse_swt_internal_gtk_OS_G_1OBJECT_1TYPE+0x0
Summary: Crash in C [libswt-pi3-gtk-4944r20.so+0x4dfb4] Java_org_eclipse_swt_interna...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.19   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-28 03:58 EDT by Paul Gardner CLA
Modified: 2022-02-21 04:34 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Gardner CLA 2021-04-28 03:58:05 EDT 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f111ea2efb4, pid=28748, tid=28766
#
# JRE version: OpenJDK Runtime Environment (15.0.2+7) (build 15.0.2+7)
# Java VM: OpenJDK 64-Bit Server VM (15.0.2+7, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libswt-pi3-gtk-4944r20.so+0x4dfb4]  Java_org_eclipse_swt_internal_gtk_OS_G_1OBJECT_1TYPE+0x0
#


C  [libswt-pi3-gtk-4944r20.so+0x4dfb4]  Java_org_eclipse_swt_internal_gtk_OS_G_1OBJECT_1TYPE+0x0
j  org.eclipse.swt.accessibility.Accessible.<init>(Lorg/eclipse/swt/widgets/Control;)V+13
j  org.eclipse.swt.accessibility.Accessible.internal_new_Accessible(Lorg/eclipse/swt/widgets/Control;)Lorg/eclipse/swt/accessibility/Accessible;+5
j  org.eclipse.swt.widgets.Control._getAccessible()Lorg/eclipse/swt/accessibility/Accessible;+9
j  org.eclipse.swt.widgets.Control.removeRelation()V+25
j  org.eclipse.swt.widgets.Control.release(Z)V+89
j  org.eclipse.swt.widgets.Widget.dispose()V+23


Full crash dump is referenced from 

https://github.com/BiglySoftware/BiglyBT/issues/2087#issuecomment-828048907
Comment 1 Soraphol (Paul) Damrongpiriyapong CLA 2021-05-14 16:44:34 EDT 
Hello, I downloaded the program and tried to reproduce it following the instructions from the Github PR. I was not able to reproduce the crash, is it possible you could create a reproduction snippet in SWT. 

Thanks, Paul
Comment 2 Paul Gardner CLA 2021-05-15 07:13:39 EDT 
It is a user reported issue, not something I have encountered.

When I worked in mainframe development in the 1980s we used to get crash dumps delivered as boxes and boxes of paper, often manually redacted by the customer with black ink or even cut out with scissors. We then tried to figure out the cause from the diagnostic data - perhaps you can do the same!
Comment 3 Paul Gardner CLA 2021-05-15 08:48:55 EDT 
Here's another user with the same issue:

https://github.com/BiglySoftware/BiglyBT/issues/2102#issuecomment-841653354
Comment 4 Paul Gardner CLA 2021-05-15 09:03:07 EDT 
I would have to ask why the code is creating a new 'Accessible' object during the disposal of the control, perhaps that is the cause?
Comment 5 Alexander Kurtakov CLA 2022-02-21 04:12:13 EST 
Is this still an issue?
Comment 6 Paul Gardner CLA 2022-02-21 04:23:32 EST 
Did anyone ever investigate why a new "Accessible" object was being created during the DESTRUCTION of a control?
Comment 7 Alexander Kurtakov CLA 2022-02-21 04:34:39 EST 
(In reply to Paul Gardner from comment #6)
> Did anyone ever investigate why a new "Accessible" object was being created
> during the DESTRUCTION of a control?

Not that I know. It would be nice of you if you do so.