Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ABdownload Manager crashes in the new Version #364

Open
farid220 opened this issue Jan 13, 2025 · 9 comments
Open

ABdownload Manager crashes in the new Version #364

farid220 opened this issue Jan 13, 2025 · 9 comments

Comments

@farid220
Copy link

farid220 commented Jan 13, 2025

Hi
First of all thanks for your great app.

I updated the app to latest version as of today (1.5.1) but I noticed that it doesn't start. I used the cli to call the app and this the log:

# A fatal error has been detected by the Java Runtime Environment:
#            
#  SIGSEGV (0xb) at pc=0x00007f6c51cbf6ab, pid=14729, tid=14834
#
# JRE version: OpenJDK Runtime Environment JBR-17.0.12+1-1207.37-nomod (17.0.12+1) (build 17.0.12+1-b1207.37)
# Java VM: OpenJDK 64-Bit Server VM JBR-17.0.12+1-1207.37-nomod (17.0.12+1-b1207.37, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame: 
# C  [libgdk-x11-2.0.so.0+0x526ab]  gdk_display_open+0x6b
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/farid/core.14729) 
#
# If you would like to submit a bug report, please visit:
#   https://youtrack.jetbrains.com/issues/JBR
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
@sabamdarif
Copy link

sabamdarif commented Jan 21, 2025

i have this same issue in v1.5.1

System: Fedora Linux 41

DE: GNOME 47

./ABDownloadManager

SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fa64c0726ab, pid=7403, tid=7516
#
# JRE version: OpenJDK Runtime Environment JBR-17.0.12+1-1207.37-nomod (17.0.12+1) (build 17.0.12+1-b1207.37)
# Java VM: OpenJDK 64-Bit Server VM JBR-17.0.12+1-1207.37-nomod (17.0.12+1-b1207.37, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libgdk-x11-2.0.so.0+0x526ab]  gdk_display_open+0x6b
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/arif/.local/ABDownloadManager/bin/core.7403)
#
JNI global refs:
JNI global refs: 169, weak refs: 51

JNI global refs memory usage: 2131, weak refs: 865

Process memory usage:
Resident Set Size: 198536K (3% of 5896572K total physical memory with 130308K free physical memory)

OOME stack traces (most recent first):
Classloader memory used:
Loader jdk.internal.loader.ClassLoaders$AppClassLoader                                 : 2595K
Loader bootstrap                                                                       : 2267K
Loader jdk.internal.loader.ClassLoaders$PlatformClassLoader                            : 8962B
Loader jdk.internal.reflect.DelegatingClassLoader                                      : 3011B

# An error report file with more information is saved as:
# /home/arif/.local/ABDownloadManager/bin/hs_err_pid7403.log
#
# If you would like to submit a bug report, please visit:
#   https://youtrack.jetbrains.com/issues/JBR
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
[1]    7403 IOT instruction (core dumped)  ./ABDownloadManager

but there is one thing i noticed that in kde plasma deestop environment i have no issue at all it's only happening on gnome.
Here is the log:-
hs_err_pid7403.log

@sabamdarif
Copy link

same in 1.5.2 too

@farid220
Copy link
Author

same in 1.5.2 too

I tested the this new version. Still I can't launch it on Fedora 41.

@amir1376
Copy link
Owner

amir1376 commented Jan 21, 2025

Hello guys. this error is not related to the app. its about internal native library. I don't know what is happened yet.

@farid220
Copy link
Author

Hello guys. this error is not related to the app but the compose library. I don't know what is happened yet.

No hard feelings. If you need to test something or if you need output or logs just say.

@amir1376
Copy link
Owner

amir1376 commented Jan 21, 2025

Guys I can't reproduce it in my system. after I compare two versions 1.5.0 and 1.5.1 (which app breaks here)
the most important thing that I think it may cause this problem is that in v1.5.1 I've added an external library dorkbox/SystemTray for better Linux system tray look and feel.
this library requires some dependencies to work properly please read their notes. (one important thing is that make sure you have the app-indicator dependency)

Further investigations

Unfortunately the crash log you gave me is not happened in jvm but native (which I don't have control on it and don't know where it exactly happened) . so I can't simply debug it on my own let alone this problem not even happens for me.

If you guys can compile and run the app from the source code on your system.

  1. try to run the app from the master branch first
  2. if the previous step fails with the error like you gave me, then I made some changes in this branch ( I removed the library and use a way like it was in v1.5.0 ) for you to test it just use this branch that I created and run it. let see if it works or not.

if it works then the problem rises from that external library and we should move the issue there.

@sabamdarif
Copy link

yes it's right that it's not a problem of the rather a problem of gnome desktop it self, because i was using this fine in kde desktop, then problem appear whenever i use gnome ( specially gnome 47 ), because i used it in gnome 46 that time i have no issue at all.
let me try those fixes, i will let you know what happened

@sabamdarif
Copy link

yes this branch fix that problem https://github.com/amir1376/ab-download-manager/tree/tmp/dont-use-external-library-system-tray-in-linux

@farid220
Copy link
Author

Guys I can't reproduce it in my system. after I compare two versions 1.5.0 and 1.5.1 (which app breaks here) the most important thing that I think it may cause this problem is that in v1.5.1 I've added an external library dorkbox/SystemTray for better Linux system tray look and feel. this library requires some dependencies to work properly please read their notes. (one important thing is that make sure you have the app-indicator dependency)

Further investigations

Unfortunately the crash log you gave me is not happened in jvm but native (which I don't have control on it and don't know where it exactly happened) . so I can't simply debug it on my own let alone this problem not even happens for me.

If you guys can compile and run the app from the source code on your system.

1. try to run the app from the `master` branch first

2. if the previous step fails with the error like you gave me, then I made some changes in this [branch](https://github.com/amir1376/ab-download-manager/tree/tmp/dont-use-external-library-system-tray-in-linux) ( I removed the library and use a way like it was in `v1.5.0` ) for you to test it just use this branch that I created and run it. let see if it works  or not.

if it works then the problem rises from that external library and we should move the issue there.

I can confirm this branch works. I did take a look on the library you mentioned and I saw last commit was 11 months ago. I don't believe the maintainer is expected to be active anytime soon. Is there another workaround for the SystemTray feature you may want to use instead of this library?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants