Segmentation fault

Errors, malfunctions, website typos.
Post Reply
giadawlk
F5 - Eucalyptus
Posts: 6
Joined: Tue Nov 10, 2020 2:45 pm

Segmentation fault

Post by giadawlk » Fri Nov 13, 2020 2:34 pm

Hi, trying out appimage 0.16.4 on Ubuntu Studio 20.04. Starts ok. Enable logging to file, save, restart. Enable Jack for audio transport (not midi yet), save, close. On attempting to restart, I get a seg fault.

me@machine:~$ ~/apps/giada/G*
[init] Giada 0.16.4
[init] Build date: Sep 23 2020
[init] Dependencies:
[init] FLTK - 1.3.4
[init] RtAudio - 5.1.0
[init] RtMidi - 3.0.0
[init] Libsamplerate
[init] Libsndfile - libsndfile-1.0.28
[init] JSON for modern C++ - 3.7.3
[init] JUCE - 5.3.2
[midiMapConf::init] scanning midimaps directory '/home/me/.giada/midimaps/'...
[midiMapConf::init] unable to scan midimaps directory!
Segmentation fault (core dumped)

Contents of log:
[midiMapConf::read] midimap not specified, nothing to do
[init] MIDI map read failed!
[KA] using system 0x0
[KA] No API available, nothing to do!
[mixer::init] buffers ready - framesInSeq=88200, framesInBuffer=0
[KM] using system 0x2
[KM] 3 output MIDI ports found
0) Midi Through:Midi Through Port-0 14:0
1) microKEY-25:microKEY-25 MIDI 1 28:0
2) Hydrogen:Hydrogen Midi-In 129:0
[KM] 3 input MIDI ports found
0) Midi Through:Midi Through Port-0 14:0
1) microKEY-25:microKEY-25 MIDI 1 28:0
2) Hydrogen:Hydrogen Midi-Out 129:1
[init] All subwindows and UI thread closed
[init] configuration saved
[init] PluginHost cleaned up
[init] Giada 0.16.4 closed


Maybe I'll try an older appimage and see what changes. I also have 0.15.4 installed from the distro's repo (issue: viewtopic.php?f=2&t=1590)

What else do you need?
Thanks!

giadawlk
F5 - Eucalyptus
Posts: 6
Joined: Tue Nov 10, 2020 2:45 pm

Re: Segmentation fault

Post by giadawlk » Fri Nov 13, 2020 2:53 pm

Did some more testing, and actually made some good progress with 0.16.1... farther than I got with 0.15.4.

0.16.2, ~.3, and ~.4 all seg fault.

Thanks!

mctom
F9 - Lavender
Posts: 52
Joined: Sat Oct 06, 2018 1:19 pm
Location: Gdansk, Poland

Re: Segmentation fault

Post by mctom » Sat Nov 14, 2020 5:45 pm

Sorry, I missed this one. :)
Anyway, this is a known bug and has been fixed, so the upcoming version 0.17 will be free from it.
A workaround exist. The reason for the segfault are the "-1" values stored in giada.conf file. Change these to "0" and it should work. :)

mctom
F9 - Lavender
Posts: 52
Joined: Sat Oct 06, 2018 1:19 pm
Location: Gdansk, Poland

Re: Segmentation fault

Post by mctom » Sat Nov 14, 2020 5:46 pm

BTW I also had MicroKEY, great piece of gear you got there. :)

giadawlk
F5 - Eucalyptus
Posts: 6
Joined: Tue Nov 10, 2020 2:45 pm

Re: Segmentation fault

Post by giadawlk » Wed Nov 18, 2020 1:39 pm

Microkey is not horrible ;)

By the way, 0.17 still seg faults.

Changing the -1 to 0 allows it to start. I have not been able to validate if it is functional beyond that... perhaps in the next day or so.

Thanks!

mctom
F9 - Lavender
Posts: 52
Joined: Sat Oct 06, 2018 1:19 pm
Location: Gdansk, Poland

Re: Segmentation fault

Post by mctom » Wed Nov 18, 2020 7:56 pm

giadawlk wrote:
Wed Nov 18, 2020 1:39 pm
By the way, 0.17 still seg faults.
Does it segfault with the old giada.conf in place, or after you let it create a new one?
0.17 version should create valid conf files, but still might segfault if the config has been broken by an earlier version.

giadawlk
F5 - Eucalyptus
Posts: 6
Joined: Tue Nov 10, 2020 2:45 pm

Re: Segmentation fault

Post by giadawlk » Wed Nov 18, 2020 11:36 pm

Starting fresh, it wrecks. Just re-verified. I tried setting it to Alsa, and that doesn't break. Just Jack (well, I didn't try anything other than Jack and Alsa).

Thanks!

mctom
F9 - Lavender
Posts: 52
Joined: Sat Oct 06, 2018 1:19 pm
Location: Gdansk, Poland

Re: Segmentation fault

Post by mctom » Thu Nov 19, 2020 8:31 am

Thanks for pointing that out, I thought this problem has been already fixed. Gotta reopen the github issue!

Post Reply