Re: [Audacity-devel] Changes for crash on logout from windows

[Vaughan J. <va...@au...>]

Thanks for your effort, Steve.

We don't have a bug entry for that, and I cannot replicate the problem.

On 3/1/2012 3:00 PM, Gale Andrews wrote:
> 
> | From Vaughan Johnson <va...@au...> 
> | Thu, 01 Mar 2012 12:55:35 -0800
> | Subject: [Audacity-devel] Changes for crash on logout from windows
>> Thanks, I'll take a look at it.
>>
>> - v
> 
> Steve (Hodgin) mentioned this on feedback@ last month. 
> 
> I've never been able to lose data from it though. It happens AFAICT 
> only if Audacity is running with an empty window and no unsaved  
> changes. 
> 
> If a project is open with no unsaved changes, Audacity quits cleanly.

It works perfectly fine on my Win 7 system, whether Audacity has an
empty project or one with content, in release build or debug. Audacity
just quits.


> 
> If there are unsaved changes, Audacity comes on top with the "Save 
> Changes?" dialogue on logging out (or shutting down). If you ignore that 
> dialogue, Windows shows you that Audacity is blocking the quit and 
> asks you to cancel or force the quit. I don't know if Windows has a 
> timeout on that dialogue, but I've waited 10 minutes and there is no 
> forced log out/shut down.

And in my testing, if you force log out, then next time you start
Audacity, it puts up the crash recovery dialog, and successfully
recovers the project. So I don't know what's broken, if anything.


> 
> So unless I'm wrong, (IMO) it doesn't seem to be a mandatory release 
> blocker. Maybe only a P4.  

I agree. I don't even know the steps to reproduce this bug.

Thanks for the additional info, Gale.

Steve, please give us more info on how to reproduce this, but preferably
after we release 2.0 (in a few days, we hope!).

- V


> 
> 
> 
> 
> Gale 
> 
> 
>  
>> On 3/1/2012 11:09 AM, Steve Hodgin wrote:
>>> The changes here are an attempt to fix a crash of Audacity when it is
>>> running and the user logs out of their Windows 7 user account.
>>>  
>>> After I made these changes though, I still get an assert failure, from
>>> wxASSERT(mRef > 0) in DirManager::Deref() (called from OnCloseWindow as
>>> mDirManager->Deref();).   It looks like mDirManager is getting
>>> overwritten, with all the memory being set to 0xDD, but when I try
>>> looking at this in the debugger, the problem does not happen.
>>>  
>>> The changes in the patch allow the shut-down to get to the mDirManager
>>> problem though instead of crashing due to null pointers.
>>>  
>>> Steve Hodgin
> 
> 
> 
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>