I have been, and will be, swamped with gigs until Monday. Have only had a
few minutes here and there to code--been focusing on the "Disappearing
Window" bug exclusively. Monday I will see where the "too many project
windows" bug leads (if I can figure it out). I did post something I thought
germane but got no response (to paraphrase):
AudacityProject * p = new AudacityProject (...);
p->DoSomeStuff();
p->SomethingElse();
What happens if "new" fails (we do not test for p==NULL)? Furthermore, what
happens if SomethingElse() calls "new" and never tests the return? There of
a number of both cases throughout Audacity.
--Ed
> -----Original Message-----
> From:
[hidden email] [mailto:
[hidden email]]
> Sent: Saturday, October 24, 2009 2:33 PM
> To:
[hidden email]
> Subject: [Audacity-devel] Problem with too many project windows WAS; [re]
> final Disappearing Window patch
>
>
> Gale Andrews wrote:
> > > You didn't say anything about my question "what progress did you
> > > make Ed with the problem when you reach the limit for the number of
> > > windows that Audacity can handle?"
> >
> > [Ed:]
> > I realize that this problem was identified during the course of
> > investigating the "Disappearing Window" bug. It is not related. If you
> > would like to create a new bug I would suggest starting a new thread
> > and entering it in the formal database (it might be a good test case
> > for the new database interface which was talked about earlier).
> > Potential bug: When a large number of project windows open Audacity
> becomes unresponsive.
>
> I know the issue is already there in for example 1.3.9, and separate.
> I was just wondering if you had any further comments or test results
beyond
> what you already mentioned earlier in the original thread.
>
> Incidentally on Ubuntu (with no other GUI programs open), I launched 80
> new Audacity project windows without any apparent strain. On Win XP with
> e-mail, clipboard, document program and Firefox (30 tabs in four
> windows) open, the limit for Audacity windows is about 23 or so. That
limit
> does not seem to be reduced if I generate a 20 minute tone and paste it
into
> each new window.
>
> I'm inclined to think it's really a P5 (not worth release noting) to see
if we can
> handle the problem more elegantly when it occurs?
>
>
>
> Gale
>
>
>
----------------------------------------------------------------------------
--
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA is
the
> only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>
http://p.sf.net/sfu/devconference> _______________________________________________
> audacity-devel mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/audacity-devel------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
