Linux Studio Plugins Project / Tickets / #11 1.0.24 keeps crashing Ardour

SadKo - 2017-05-22

That's something new. I can't see anyting relative to LSP Plugins in stack trace.
What version of Ardour are you using?

Last edit: SadKo 2017-05-22

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- funkmuscle - 2017-05-22
  
  Oh sorry, 5.9
  
  Last edit: SadKo 2017-05-23
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - CrocoDuck o'Ducks - 2017-05-22
    
    Hi there!
    
    Did you install LSP plugins from the AUR? If so, which packages?
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - funkmuscle - 2017-05-22
      
      Dude both lv2 and lxvst.
      
      Last edit: SadKo 2017-05-23
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - SadKo - 2017-05-23
        
        According to the information from this topic: https://linuxmusicians.com/viewtopic.php?f=24&t=17123&start=15
        you had no issues with new empty session. Also valgrind didn't find something critical.
        Have you launched LSP Plugins under Ardour+Valgrind and then added DrumGizmo to see what happens in valgrind?
        Currently it all looks out like heap corruption.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        funkmuscle - 2017-05-23
        
        yes it was running with DrumGizmo but the memcheck enabled I'm not sure.
        I ran it like this: valgrind --leak-check=full ardour5
        
        Last edit: SadKo 2017-05-23
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        SadKo - 2017-05-23
        
        Please try to run with --tool=memcheck option
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

CrocoDuck o'Ducks - 2017-05-23

I think I reproduced the issue.

My platform:

Linux arch 4.9.29-1-lts #1 SMP Sat May 20 17:35:48 CEST 2017 x86_64 GNU/Linux

Software versions:

Ardour5.9.0 (built using 5.9 and GCC version 6.3.1 20170306)

LSP plugins from AUR:
local/lsp-plugins-lv2-bin 1.0.23-1
Linux Studio Plugins: LV2 format
local/lsp-plugins-lxvst-bin 1.0.24-1
Linux Studio Plugins: VST format

Drumgizmo from AUR:
local/drumgizmo 0.9.13-2 (lv2-plugins)
an open source cross-platform drum plugin and stand-alone application (lv2)

I cannot get any crash by using LSP plugins alone, but my session crashes when I try to load a drumkit into drumgizmo.

Here what valgrind --leak-check=full --tool=memcheck ardour5 thinks:

$ valgrind --leak-check=full --tool=memcheck ardour5
==28172== Memcheck, a memory error detector
==28172== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==28172== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==28172== Command: /usr/bin/ardour5
==28172==
==28173==
==28173== HEAP SUMMARY:
==28173== in use at exit: 40,054 bytes in 575 blocks
==28173== total heap usage: 3,247 allocs, 2,672 frees, 177,786 bytes allocated
==28173==
==28173== 11 bytes in 1 blocks are definitely lost in loss record 83 of 295
==28173== at 0x4C2AF1F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==28173== by 0x47224D: xmalloc (in /usr/bin/bash)
==28173== by 0x46BE88: set_default_locale (in /usr/bin/bash)
==28173== by 0x41A048: main (in /usr/bin/bash)
==28173==
==28173== LEAK SUMMARY:
==28173== definitely lost: 11 bytes in 1 blocks
==28173== indirectly lost: 0 bytes in 0 blocks
==28173== possibly lost: 0 bytes in 0 blocks
==28173== still reachable: 40,043 bytes in 574 blocks
==28173== suppressed: 0 bytes in 0 blocks
==28173== Reachable blocks (those to which a pointer was found) are not shown.
==28173== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==28173==
==28173== For counts of detected and suppressed errors, rerun with: -v
==28173== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
==28174==
==28174== HEAP SUMMARY:
==28174== in use at exit: 41,687 bytes in 632 blocks
==28174== total heap usage: 3,502 allocs, 2,870 frees, 183,240 bytes allocated
==28174==
==28174== 11 bytes in 1 blocks are definitely lost in loss record 83 of 308
==28174== at 0x4C2AF1F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==28174== by 0x47224D: xmalloc (in /usr/bin/bash)
==28174== by 0x46BE88: set_default_locale (in /usr/bin/bash)
==28174== by 0x41A048: main (in /usr/bin/bash)
==28174==
==28174== LEAK SUMMARY:
==28174== definitely lost: 11 bytes in 1 blocks
==28174== indirectly lost: 0 bytes in 0 blocks
==28174== possibly lost: 0 bytes in 0 blocks
==28174== still reachable: 41,676 bytes in 631 blocks
==28174== suppressed: 0 bytes in 0 blocks
==28174== Reachable blocks (those to which a pointer was found) are not shown.
==28174== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==28174==
==28174== For counts of detected and suppressed errors, rerun with: -v
==28174== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
==28183==
==28183== HEAP SUMMARY:
==28183== in use at exit: 45,293 bytes in 793 blocks
==28183== total heap usage: 3,880 allocs, 3,087 frees, 209,073 bytes allocated
==28183==
==28183== 11 bytes in 1 blocks are definitely lost in loss record 83 of 349
==28183== at 0x4C2AF1F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==28183== by 0x47224D: xmalloc (in /usr/bin/bash)
==28183== by 0x46BE88: set_default_locale (in /usr/bin/bash)
==28183== by 0x41A048: main (in /usr/bin/bash)
==28183==
==28183== LEAK SUMMARY:
==28183== definitely lost: 11 bytes in 1 blocks
==28183== indirectly lost: 0 bytes in 0 blocks
==28183== possibly lost: 0 bytes in 0 blocks
==28183== still reachable: 45,282 bytes in 792 blocks
==28183== suppressed: 0 bytes in 0 blocks
==28183== Reachable blocks (those to which a pointer was found) are not shown.
==28183== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==28183==
==28183== For counts of detected and suppressed errors, rerun with: -v
==28183== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale
Ardour5.9.0 (built using 5.9 and GCC version 6.3.1 20170306)
ardour: [INFO]: Your system is configured to limit Ardour to only 4096 open files
ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config
ardour: [INFO]: Loading user configuration file /home/crocoduck/.config/ardour5/config
ardour: [INFO]: CPU vendor: GenuineIntel
ardour: [INFO]: AVX-capable processor
ardour: [INFO]: CPU brand: Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: Loading default ui configuration file /etc/ardour5/default_ui_config
ardour: [INFO]: Loading user ui configuration file /home/crocoduck/.config/ardour5/ui_config
Color shuttle bg not found
ardour: [INFO]: Loading color file /usr/share/ardour5/themes/dark-ardour.colors
ardour: [INFO]: Loading ui configuration file /etc/ardour5/clearlooks.rc
ardour: [INFO]: Loading ui configuration file /etc/ardour5/clearlooks.rc
Found nothing along /home/crocoduck/.config/ardour5/templates:/usr/share/ardour5/templates
run dialog
protocol Open Sound Control (OSC) active ? 0
protocol Steinberg CC121 active ? 0
protocol Generic MIDI active ? 0
protocol PreSonus FaderPort8 active ? 0
protocol Ableton Push 2 active ? 0
protocol PreSonus FaderPort active ? 0
protocol Mackie active ? 0
Scanning folders for bundled LV2s: /usr/lib/ardour5/LV2
KP is ardour.keys
Set cursor set to default
Set buffering params to 262144|131072|10|10
ie_midi: 0xd1468d0
ie_midi: 0xd1468d0
protocol Open Sound Control (OSC) active ? 0
protocol Steinberg CC121 active ? 0
protocol Generic MIDI active ? 0
protocol PreSonus FaderPort8 active ? 0
protocol Ableton Push 2 active ? 0
protocol PreSonus FaderPort active ? 0
protocol Mackie active ? 0
set state: 1
Set buffering params to 262144|131072|10|10
Skip explicit buffer seconds, preset in use
Skip explicit buffer seconds, preset in use
Floating point exception (core dumped)

Last edit: SadKo 2017-05-23

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- SadKo - 2017-05-23
  
  I'm not sure but it looks like valgrind is looking for leaks in bash instead of Ardour.
  Maybe the better way would be to copy ardour5 script to ardour5.valgrind and modify it to force to run Ardour under valgrind?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

CrocoDuck o'Ducks - 2017-05-23

Ehm... uhm... embarrassing moment... I think the reason why the session crashed is because I loaded the midimap instead of the drumkit by accident. This seems to crash Ardour, also for sessions with drumgizmo only. So I think that actually I still have to properly reproduce this.

I think you are right about valgrind looking at bash. I did as you suggested and edited the last line of ardour5.valgrind to this:

exec $GDB valgrind --leak-check=full --tool=memcheck /usr/lib/ardour5/ardour-5.9.0 "$@"

It makes a very different output (much much longer). Couldn't manage to capture a crash yet tho, the program slows down a lot and seems like I have a lot more to wait before it crashes. I will try again soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- funkmuscle - 2017-05-23
  
  ok so since I'm new to valgrind, what's the exact execution to run this
  test?
  
  Last edit: SadKo 2017-05-24
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - CrocoDuck o'Ducks - 2017-05-24
    
    I am not too sure as I am new to valgrind too. However, seems to me that we must ensure valgrind operates with /usr/lib/ardour5/ardour-5.9.0, which to operate properly needs the environment variables and checks operated by the /usr/bin/ardour5 script. So, I did this:
    
    cp /usr/bin/ardour5 /usr/bin/ardour5.valgrind nano /usr/bin/ardour5.valgrind
    
    Locate this line (should be the last one):
    
    exec $GDB /usr/lib/ardour5/ardour-5.9.0 "$@"
    
    and change it to
    
    exec $GDB valgrind --leak-check=full --tool=memcheck /usr/lib/ardour5/ardour-5.9.0 "$@"
    
    save and exit.
    
    Then, everytime we call this in the terminal
    
    ardour5.valgrind
    
    we will launch a "valgrind version" of Ardour. Be aware that Ardour launched in this way appears to be much less responsive (it is very slow).
    
    Since we are pretty much running the same system maybe I can have a look at your session to try to reproduce the issue. Could you attach the .ardour file of your crashing session?
    
    Also, which version of drumgizmo are you using? Is that from AUR too? Is it the git one?
    
    Last edit: CrocoDuck o'Ducks 2017-05-24
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - SadKo - 2017-05-24
      
      Yes, because valgrind controls and emulates all memory writes, it's so slooow. But memcheck tool helps to capture all illegal memory writes.
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - funkmuscle - 2017-05-24
      
      I get this:
      $ ardour5.valgrind
      valgrind: /usr/lib/ardour5/ardour-5.9.0: No such file or directory
      
      Last edit: SadKo 2017-05-24
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - funkmuscle - 2017-05-24
        
        and now Ardour will launch but as soon as I got to edit the LSP Plugin, it
        opens with a blank screen then Ardour freezes and crashes.
        
        attached is the .ardour file you requested. it's just a simple drum beat to
        test the issue.
        
        Last edit: SadKo 2017-05-24
        
        more kit testing.ardour
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        SadKo - 2017-05-24
        
        Do you have some output of valgrind?
        
        Also I would like to ask you to not to reply with emails because sf.net handles them poorly and I'm required to edit all your messages. Please write directly to the topic on the site.
        
        Thanks.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        CrocoDuck o'Ducks - 2017-05-24
        
        Thank you funkmuscle. Unfortunately I cannot make your session to crash on my system. I wonder what's going on with your /usr/lib/ardour5/ardour-5.9.0: I think it should be there. Did you install ardour from repos or ardour-git from AUR? Can you show us the contents of /usr/bin/ardour5?
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

funkmuscle - 2017-05-24

Croc I've tried both ardour. the one from repo and the one from git. currently running git.
is this what you wanted:

$ ls ardour-5.9.13 libaudiographer.so.0 libpbd.so ardour-exec-wrapper libaudiographer.so.0.0.0 libpbd.so.4 ardour-request-device libcanvas.so libpbd.so.4.1.0 ardour-vst-scanner libcanvas.so.0 libptformat.so backends libcanvas.so.0.0.0 libptformat.so.0 engines libevoral.so libptformat.so.0.0.0 hardour-5.9.13 libevoral.so.0 libqm-dsp.a libardouralsautil.so libevoral.so.0.0.0 libtimecode.so libardouralsautil.so.0 libgtkmm2ext.so luasession libardouralsautil.so.0.0.1 libgtkmm2ext.so.0 LV2 libardourcp.so libgtkmm2ext.so.0.8.3 panners libardour.so libhidapi.a sanityCheck libardour.so.3 libmidipp.so surfaces libardour.so.3.0.0 libmidipp.so.4 vamp libaudiographer.so libmidipp.so.4.1.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- CrocoDuck o'Ducks - 2017-05-24
  
  Not exactly, but that actually clarifies things anyway. I was thinking of looking at this:
  
  cat /usr/bin/ardour5
  
  while what you posted looks like what I would get out of this:
  
  ls /usr/lib/ardour5/
  
  but I can still see that you are on Ardour 5.9.13, from git. I am running 5.9.0 from repos instead: that's why my change in ardour5.valgrind does not work for you.
  
  If you run cat /usr/bin/ardour5 I would expect the last line to look like this then:
  
  exec $GDB /usr/lib/ardour5/ardour-5.9.13 "$@"
  
  So edit the corresponding line in ardour5.valgrind to this:
  
  exec $GDB valgrind --leak-check=full --tool=memcheck /usr/lib/ardour5/ardour-5.9.13 "$@"
  
  In other words, just put valgrind --leak-check=full --tool=memcheck just after exec $GDB, leaving all the rest as in the original /usr/bin/ardour5 file. This should allow us to get ardour5 through valgrind for real. Then we will have a good report when you produce a crash. In case it wasn't clear, the original /usr/bin/ardour5 is not meant to be edited (that's why we crated ardour5.valgrind).
  
  Can you also repost the output of this?
  
  pacman -Qs drumgizmo
  
  I am gonna try to install Ardour git then and check whether I can crash the session with that.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - CrocoDuck o'Ducks - 2017-05-25
    
    Got Ardour from ardour-git, but still unable to reproduce the issue. Got a different version though:
    
    Ardour5.9.33 (built using 5.9-33-g244313f43 and GCC version 6.3.1 20170306)
    
    Can you also repost your full version?
    
    ardour5 --version
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

funkmuscle - 2017-05-25

Ardour5.9.13 (built using 5.9-13-gb3fb75fea and GCC version 6.3.1 20170306)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- CrocoDuck o'Ducks - 2017-05-29
  
  I did few more tests using your very same Ardour version and session file but I still cannot make it crash on my system. That's pretty weird. I wonder whether I should try with all the session files in place. I get that the session "more kit testing" (which causes the crash in your system) is pretty small, with just one midi track. Try to compress the whole session folder, if it is just few MB perhaps it will fit in the attachments.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

funkmuscle - 2017-05-30

Ok, so as I tried to do an update with pacman, I couldn't due to some gcc and gcc-multilib issues. For some reason gcc and gcc-multilib were both installed even though when I first switched to multilib, it said it would replace the gcc, etc. Fixed that now. So I've done a git pull of ardour and reinstalled LSP both lv2 and lxvst.. Lv2 still crashes Ardour but the lxvst works great.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- CrocoDuck o'Ducks - 2017-05-30
  
  Interesting. Gonna try the latest version again then. If you can submit a small archive with a complete minimal crashing session it would be really appreciated. As a note, lsp-plugins-lv2-bin appears to be at version 1.0.23. Is it that version you are using?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

SadKo - 2017-12-22

How it's going with 1.1.0 release?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

1.0.24 keeps crashing Ardour

Linux Studio Plugins Project

Milestone

Searches

Help

#11 1.0.24 keeps crashing Ardour

Discussion