search

flathub / info.portfolio_performance.PortfolioPerformance

https://flathub.org/apps/details/info.portfolio_performance.PortfolioPerformance
8 stars 4 forks source link

Application consistently crashes due to segfaults in Java VM #28

Open croxxx opened 2 years ago

croxxx commented 2 years ago

Problem

In many cases the application just terminates without any further notification when clicking somewhere. The issue is consistent and can be reproduced every time by clicking on the same entries.

Currently definitely affected:

I am unfortunately not an expert in neither Java nor GTK nor Flatpak packaging, so I'm documenting this here hoping it helps troubleshoot the issue.

Notes

Logs

Console output

All errors before the fatal one reported last are occuring during normal operation. I assume they are not directly related to this crash, yet something seems off about those.


$ flatpak run info.portfolio_performance.PortfolioPerformance

Gtk-Message: 18:45:39.104: Failed to load module "xapp-gtk3-module" Gtk-Message: 18:45:39.504: Failed to load module "xapp-gtk3-module"

(process:10712): flatpak-WARNING : 18:45:39.529: Error writing credentials to socket: Error sending message: Broken pipe (Portfolio Performance:23): CRITICAL : 18:45:42.322: JNI class pointer is NULL for class org/eclipse/swt/accessibility/AccessibleObject (Portfolio Performance:23): CRITICAL : 18:45:42.322: JNI class pointer is NULL for class org/eclipse/swt/accessibility/AccessibleObject (Portfolio Performance:23): Gtk-CRITICAL : 18:45:43.574: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar (Portfolio Performance:23): Gtk-CRITICAL **: 18:45:58.650: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

#

A fatal error has been detected by the Java Runtime Environment:

#

SIGSEGV (0xb) at pc=0x00007f0d36e9762d, pid=23, tid=24

#

JRE version: OpenJDK Runtime Environment 18.9 (11.0.14+8) (build 11.0.14+8)

Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.14+8, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)

Problematic frame:

C [libgtk-3.so.0+0x39062d] gtk_widget_is_sensitive+0x1d

#

Core dump will be written. Default location: Core dumps may be processed with "/lib/systemd/systemd-coredump %P %u %g %s %t 9223372036854775808 %h" (or dumping to /home/user/core.23)

#

An error report file with more information is saved as:

/home/user/hs_err_pid23.log

Compiled method (nm) 19464 8892 n 0 org.eclipse.swt.internal.accessibility.gtk.ATK::call (native) total in heap [0x00007f0d989ef810,0x00007f0d989efbb8] = 936 relocation [0x00007f0d989ef988,0x00007f0d989ef9b8] = 48 main code [0x00007f0d989ef9c0,0x00007f0d989efbb0] = 496 oops [0x00007f0d989efbb0,0x00007f0d989efbb8] = 8 #

If you would like to submit a bug report, please visit:

https://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.

#


### Dump written to home directory
[hs_err_pid23.log](https://github.com/flathub/info.portfolio_performance.PortfolioPerformance/files/8208711/hs_err_pid23.log)
roshanshariff commented 1 year ago

It's possible this error could have been resolved by a recent change (#61). I'd appreciate it if you could test again with the current Flatpak version and see if you still get these crashes.

croxxx commented 1 year ago

I can confirm the Flatpak app is currently working fine for me. The details displayed in the application itself are:

Version: 0.62.0 (Apr. 2023)
Platform: linux, x86_64
Java: 17.0.6+10, Flathub

flatpak info shows:

[...]
          Commit: 4ebbbdaab2895cc78f1168b4a22d88b2a80dceac8993abc4b261278a4ace4…
          Parent: e7c5c41f480364b846d2b8bb8ef62992d8949ce5bc399ae954b48030dddb0…
         Subject: Add IPC namespace sharing permission (#61) (6bdd4427)
            Date: 2023-04-23 03:14:15 +0000

Interestingly enough, the Java version reported on the UI now is different from the one in my initial crash report (OpenJDK Runtime Environment 18.9 (11.0.14+8)). It seems there were further changes in packaging since I last tested this.

As the issue is no longer present for me it should be fine to close this, if no one else is affected.

oyren commented 1 year ago

Hey thank you, i was affected by this issue and updated to the current version.

Name                                              Application ID                                              Version             Branch                   Installation
Portfolio Performance                             info.portfolio_performance.PortfolioPerformance             0.62.0              stable                   system

I can't report if the crashes are gone, since the application now constantly crashes on startup (not sure if this is related):

 > flatpak run info.portfolio_performance.PortfolioPerformance

(process:2): Gtk-WARNING **: 19:14:39.523: Locale not supported by C library.
    Using the fallback 'C' locale.
WARNING: Using incubator modules: jdk.incubator.foreign, jdk.incubator.vector

(process:29): Gtk-WARNING **: 19:14:40.177: Locale not supported by C library.
    Using the fallback 'C' locale.

** (Portfolio Performance:29): CRITICAL **: 19:14:44.840: JNI class pointer is NULL for class org/eclipse/swt/accessibility/AccessibleObject

** (Portfolio Performance:29): CRITICAL **: 19:14:44.841: JNI class pointer is NULL for class org/eclipse/swt/accessibility/AccessibleObject

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details

flatpak info:

      Commit: 4ebbbdaab2895cc78f1168b4a22d88b2a80dceac8993abc4b261278a4ace497d
      Parent: e7c5c41f480364b846d2b8bb8ef62992d8949ce5bc399ae954b48030dddb0c15
     Subject: Add IPC namespace sharing permission (#61) (6bdd4427)
        Date: 2023-04-23 03:14:15 +0000
roshanshariff commented 1 year ago

Thanks for the feedback! @croxxx, I'm happy to hear the problem is resolved for you. The JVM version has indeed been updated recently.

@oyren, I'll keep this bug open to track the crashes you're experiencing. I'm afraid I don't know how to go about narrowing down the root cause. The error/warning messages seem harmless, since I get them too (except for the locale error) but without crashes.

roshanshariff commented 1 year ago

@oyren, we've identified a possible reason for these crashes: buchen/portfolio#3418. A fix has now been published to Flathub. Perhaps you could test it again and see if your problem is gone.

oyren commented 1 year ago

@roshanshariff thanks, sadly i can't report any improvements, with flatpak info info.portfolio_performance.PortfolioPerformance:

          ID: info.portfolio_performance.PortfolioPerformance
         Ref: app/info.portfolio_performance.PortfolioPerformance/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 0.64.4
     License: EPL-2.0
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 247.3?MB
     Runtime: org.gnome.Platform/x86_64/43
         Sdk: org.gnome.Sdk/x86_64/43

      Commit: 99a746f74c9d6d3a7437807df345315ce917f186c87ef5fb034b915e01290b52
      Parent: d215a05a419831ffa175f04725e86275003d50e8349e5576d2610ed53bafdfea
     Subject: Update 2 modules (ede05853)
        Date: 2023-07-15 14:48:57 +0000