ardour-3.5.403~dfsg-3 crashed with SIGSEGV in ProcessorWindowProxy::processor_going_away()

[tomdoceara]

travou ao mudar plugin em realtime

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: ardour3 3.5.403~dfsg-3
ProcVersionSignature: Ubuntu 3.19.0-7.7-lowlatency 3.19.0
Uname: Linux 3.19.0-7-lowlatency x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sun Mar 1 08:34:17 2015
ExecutablePath: /usr/lib/ardour3/ardour-3.5.403~dfsg-3
InstallationDate: Installed on 2015-03-01 (0 days ago)
InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Alpha amd64 (20150126)
ProcCmdline: /usr/lib/ardour3/ardour-3.5.403~dfsg-3
Signal: 11
SourcePackage: ardour3
Stacktrace:
 #0 0x0000000000a8cea5 in ProcessorWindowProxy::processor_going_away() ()
 No symbol table info available.
 Backtrace stopped: Não é possível acessar a memória no endereço 0x7fff736017c8
StacktraceTop: ProcessorWindowProxy::processor_going_away() ()
Title: ardour-3.5.403~dfsg-3 crashed with SIGSEGV in ProcessorWindowProxy::processor_going_away()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

[Steve Beattie (sbeattie)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.