Description of problem: Instantiating a new audacity instance and closing the old one. Reproduce: - Open audacity - Record 14 samples in 14 different tracks รก 3-5 seconds long - Open new audacity instance from File menu - Try to close old instance w/o saving work. Result: Both audacity instances get terminated with SIGSEGV Version-Release number of selected component: audacity-2.0.2-2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: audacity crash_function: ProgressDialog::Update kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #1 ProgressDialog::Update at widgets/ProgressDialog.cpp:1329 : #2 RecursivelyRemove at DirManager.cpp:304 : #3 DirManager::CleanTempDir at DirManager.cpp:396 : #4 DirManager::~DirManager at DirManager.cpp:375 : #6 AudacityProject::OnCloseWindow at Project.cpp:2027 : #7 ProcessEventIfMatches at src/common/event.cpp:1239 : #8 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1214 : #9 wxEventHashTable::HandleEvent at src/common/event.cpp:906 : #10 ProcessEvent at src/common/event.cpp:1301 : #11 wxEvtHandler::ProcessEvent at src/common/event.cpp:1272
Created attachment 678616 [details] File: core_backtrace
Created attachment 678617 [details] File: environ
Created attachment 678618 [details] File: limits
Created attachment 678619 [details] File: backtrace
Created attachment 678620 [details] File: cgroup
Created attachment 678621 [details] File: smolt_data
Created attachment 678622 [details] File: executable
Created attachment 678623 [details] File: maps
Created attachment 678624 [details] File: dso_list
Created attachment 678625 [details] File: proc_pid_status
Created attachment 678626 [details] File: var_log_messages
Created attachment 678627 [details] File: open_fds
Created attachment 678628 [details] File: build_ids
Hi, Audacity in Fedora 17 and later has been upgraded the upstream 2.0.3 bugfix release, which includes a lot of bugfixes, and hopefully also fixes this bug. Please upgrade audacity to the 2.0.3 release and try again. If it crashes again, please let abrt file a new bug with the 2.0.3 release, which may have a different backtrace / issue. Thanks & Regards, Hans