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

jackdbus crash on jack_unload #933

Open
tavasti opened this issue May 11, 2023 · 5 comments
Open

jackdbus crash on jack_unload #933

tavasti opened this issue May 11, 2023 · 5 comments
Labels

Comments

@tavasti
Copy link

tavasti commented May 11, 2023

jackdbus crash on jack_unload

I load another audioadapter with command: jack_load -i "-d hw:Ultra -i6 -o6" ultra audioadapter

unloading it with: jack_unload ultra

After this, jackdbus will crash (will attach log file)

Environment

  • JACK Version: 1.9.17~dfsg-1
  • Operating System: linux devuan 4.0 (same as debian 11)
  • Installation: package manager

Steps To Reproduce

Assuming you have extra audio interface which has name Ultra in arecord -l

jack_load -i "-d hw:Ultra -i6 -o6" ultra audioadapter
jack_unload ultra

Expected vs. actual behavior

Expecting extra audio adapter to unload, and jack continue to work

@tavasti tavasti added the bug label May 11, 2023
@tavasti
Copy link
Author

tavasti commented May 11, 2023

jackdbus.log

@nedko
Copy link
Contributor

nedko commented May 11, 2023

8:37 2023: ERROR: Abort!
8:37 2023: ERROR: info.si_signo = 6
8:37 2023: ERROR: info.si_errno = 0
8:37 2023: ERROR: info.si_code = -6 (unknown)
8:37 2023: ERROR: info.si_addr = 0x3e80000774a
8:37 2023: ERROR: reg[00] = 0x0000000000000000
8:37 2023: ERROR: reg[01] = 0x00007fde458503b0
8:37 2023: ERROR: reg[02] = 0x0000000000000008
8:37 2023: ERROR: reg[03] = 0x0000000000000246
8:37 2023: ERROR: reg[04] = 0x00007fde45850620
8:37 2023: ERROR: reg[05] = 0x0000000000001000
8:37 2023: ERROR: reg[06] = 0x0000000000000010
8:37 2023: ERROR: reg[07] = 0x00007fde46308000
8:37 2023: ERROR: reg[08] = 0x0000000000000002
8:37 2023: ERROR: reg[09] = 0x00007fde458503b0
8:37 2023: ERROR: reg[10] = 0x00007fde45850700
8:37 2023: ERROR: reg[11] = 0x00007fde45851700
8:37 2023: ERROR: reg[12] = 0x0000000000000000
8:37 2023: ERROR: reg[13] = 0x0000000000000000
8:37 2023: ERROR: reg[14] = 0x00007fde464c8ce1
8:37 2023: ERROR: reg[15] = 0x00007fde458503b0
8:37 2023: ERROR: reg[16] = 0x00007fde464c8ce1
8:37 2023: ERROR: reg[17] = 0x0000000000000246
8:37 2023: ERROR: reg[18] = 0x002b000000000033
8:37 2023: ERROR: reg[19] = 0x0000000000000000
8:37 2023: ERROR: reg[20] = 0x0000000000000000
8:37 2023: ERROR: reg[21] = 0x0000000000005a07
8:37 2023: ERROR: reg[22] = 0x0000000000000000
8:37 2023: ERROR: Stack trace:
8:37 2023: ERROR: 1: 0x7fde464c8ce1 <gsignal+321> (/lib/x86_64-linux-gnu/libc.so.6)
8:37 2023: ERROR: End of stack trace

@nedko
Copy link
Contributor

nedko commented May 11, 2023

A stack trace with debug info will be much more useful than the currently reported one.
After building jack2 with debug info and without optimization, run jackdbus through gdb,
then crash it and obtain the better stack trace.

@nedko
Copy link
Contributor

nedko commented May 11, 2023

The crash may be related to initialization failure described in #934

@tavasti
Copy link
Author

tavasti commented May 12, 2023

Because zalsa_in and zalsa_out exist, this bug might be regarded as obsolete, and closed.

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

No branches or pull requests

2 participants