Mac build debug alerts

[Michael Chinen]

Can someone else run the mac debug build and let me know if they see a
lot of alerts on startup?  They involve RTTI: see here for further
description:
http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html

I've been hitting ignore all and they don't bug me after that, but I
doubt this is a permanent solution.  I couldn't figure out what they
meant after a few minutes on google.

Michael

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Michael Chinen]

I forgot to add that Audacity now idles on my machine at 25%-40% of
CPU (as opposed to 1% before,) and I'm trying to find out if this is
related.  I would guess the windows build does not have this problem?

On Fri, Jul 3, 2009 at 12:53 PM, Michael Chinen<[hidden email]> wrote:

> Can someone else run the mac debug build and let me know if they see a
> lot of alerts on startup?  They involve RTTI: see here for further
> description:
> http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html
>
> I've been hitting ignore all and they don't bug me after that, but I
> doubt this is a permanent solution.  I couldn't figure out what they
> meant after a few minutes on google.
>
> Michael
>

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Gale (Audacity Team)]

| From Michael Chinen <[hidden email]>
| Fri, 3 Jul 2009 13:08:30 -0700
| Subject: [Audacity-devel] Mac build debug alerts
> I forgot to add that Audacity now idles on my machine at 25%-40% of
> CPU (as opposed to 1% before,) and I'm trying to find out if this is
> related.  I would guess the windows build does not have this problem?

I've only built ANSI Release and Unicode Release on Windows so far,
and idle CPU is about 5% with Auacity running, 4% if it isn't.



Gale


 

> On Fri, Jul 3, 2009 at 12:53 PM, Michael Chinen<[hidden email]> wrote:
> > Can someone else run the mac debug build and let me know if they see a
> > lot of alerts on startup?  They involve RTTI: see here for further
> > description:
> > http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html
> >
> > I've been hitting ignore all and they don't bug me after that, but I
> > doubt this is a permanent solution.  I couldn't figure out what they
> > meant after a few minutes on google.
> >
> > Michael
> >
>
> ------------------------------------------------------------------------------
> _______________________________________________
> audacity-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Dan Horgan]

On Fri, Jul 03, 2009 at 01:08:30PM -0700, Michael Chinen wrote:
> I forgot to add that Audacity now idles on my machine at 25%-40% of
> CPU (as opposed to 1% before,) and I'm trying to find out if this is
> related.  I would guess the windows build does not have this problem?

Audacity takes no more than ~4% CPU when idle on my not-particularly-fast
machine, on both Windows and Linux.

> On Fri, Jul 3, 2009 at 12:53 PM, Michael Chinen<[hidden email]> wrote:
> > Can someone else run the mac debug build and let me know if they see a
> > lot of alerts on startup?  They involve RTTI: see here for further
> > description:
> > http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html
> >
> > I've been hitting ignore all and they don't bug me after that, but I
> > doubt this is a permanent solution.  I couldn't figure out what they
> > meant after a few minutes on google.
> >
> > Michael
> >

Let me know if it seems like this is related to any of the scripting
code - at the moment I can't think of any reason why it would be though.

Dan

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Leland Lucius-4]

Michael,

I'm fairly certain that your problem has to do with your wxWidgets build.  I've gotten those messages when I've had my mucked up.  I'm at work right now, so I can't try the "Debug" configuration, but I will when I get home.  I must admit that it's probably been a few weeks since I've built it.

Leland

On Fri, Jul 3, 2009 at 2:53 PM, Michael Chinen <[hidden email]> wrote:

Can someone else run the mac debug build and let me know if they see a
lot of alerts on startup?  They involve RTTI: see here for further
description:
http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html

I've been hitting ignore all and they don't bug me after that, but I
doubt this is a permanent solution.  I couldn't figure out what they
meant after a few minutes on google.

Michael

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------------------------

_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Leland (Audacity Team)]

Leland Lucius wrote:
> Michael,
>
> I'm fairly certain that your problem has to do with your wxWidgets
> build.  I've gotten those messages when I've had my mucked up.  I'm at
> work right now, so I can't try the "Debug" configuration, but I will
> when I get home.  I must admit that it's probably been a few weeks since
> I've built it.
>
It's the building of mod-script-pipe.  Trying to figure out why.

Leland


------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Leland (Audacity Team)]

Gale Andrews wrote:

> | From Michael Chinen <[hidden email]>
> | Fri, 3 Jul 2009 13:08:30 -0700
> | Subject: [Audacity-devel] Mac build debug alerts
>> I forgot to add that Audacity now idles on my machine at 25%-40% of
>> CPU (as opposed to 1% before,) and I'm trying to find out if this is
>> related.  I would guess the windows build does not have this problem?
>
> I've only built ANSI Release and Unicode Release on Windows so far,
> and idle CPU is about 5% with Auacity running, 4% if it isn't.
>

That's really odd.  It idles at around .6% (yes, less than 1%).  Do you
have a means of profiling to see if you can find out where it's spending
all of the time?

Leland




------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Paul Livesey]

On 4 Jul 2009, at 11:18, Leland wrote:

> Gale Andrews wrote:
>> | From Michael Chinen <[hidden email]>
>> | Fri, 3 Jul 2009 13:08:30 -0700
>> | Subject: [Audacity-devel] Mac build debug alerts
>>> I forgot to add that Audacity now idles on my machine at 25%-40% of
>>> CPU (as opposed to 1% before,) and I'm trying to find out if this is
>>> related.  I would guess the windows build does not have this  
>>> problem?
>>
>> I've only built ANSI Release and Unicode Release on Windows so far,
>> and idle CPU is about 5% with Auacity running, 4% if it isn't.
>>
> That's really odd.  It idles at around .6% (yes, less than 1%).  Do  
> you
> have a means of profiling to see if you can find out where it's  
> spending
> all of the time?
>
> Leland
>

Same here, nothing in the logs and it's idling at 0.3 to 0.4%

Paul.

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Gale (Audacity Team)]

| From Leland <[hidden email]>
| Sat, 04 Jul 2009 05:18:13 -0500
| Subject: [Audacity-devel] Mac build debug alerts

> Gale Andrews wrote:
> > | From Michael Chinen <[hidden email]>
> > | Fri, 3 Jul 2009 13:08:30 -0700
> > | Subject: [Audacity-devel] Mac build debug alerts
> >> I forgot to add that Audacity now idles on my machine at 25%-40% of
> >> CPU (as opposed to 1% before,) and I'm trying to find out if this is
> >> related.  I would guess the windows build does not have this problem?
> >
> > I've only built ANSI Release and Unicode Release on Windows so far,
> > and idle CPU is about 5% with Auacity running, 4% if it isn't.
>
> That's really odd.  It idles at around .6% (yes, less than 1%).  Do you
> have a means of profiling to see if you can find out where it's spending
> all of the time?

Leland

All I have is Windows Task Manager (that I can recall). What I meant was
that if I launch my usual apps (e-mail/FF/text editor), CPU usage settles
down on 4%. If I then launch Audacity, it settles down on 5%. I deduce
from that, that Audacity is idling at about 1%, emphasis on "about".  

Like I said in another post, the 1.3.8 memory usage on launch is about
17,000 K.

Is there something else you would like me to test? If so, please tell me
what with. Remember this (XP) machine often seems to take much longer
than say Martyn's to perform effects in Audacity, with much greater
variability.  



Gale
 



------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Alec Burgess-2]

Some javascript/style in this post has been disabled (why?)

Gale Andrews ([hidden email]) wrote (in part)  (on 2009-07-04 at
12:35):
> All I have is Windows Task Manager (that I can recall). What I meant
> was that if I launch my usual apps (e-mail/FF/text editor), CPU usage
> settles down on 4%. If I then launch Audacity, it settles down on 5%.
> I deduce from that, that Audacity is idling at about 1%, emphasis on
> "about". Like I said in another post, the 1.3.8 memory usage on
> launch is about 17,000 K. Is there something else you would like me
> to test? If so, please tell me what with. Remember this (XP) machine
> often seems to take much longer than say Martyn's to perform effects
> in Audacity, with much greater variability.

Gale: (free) Process Explorer http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx will give you a better handle on what resources are being consumed by Audacity. You can d-click on its entry and see a graph showing its memory-usage and cpu%-consumption over time.


------------------------------------------------------------------------------

_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Leland (Audacity Team)]

Michael Chinen wrote:
> Can someone else run the mac debug build and let me know if they see a
> lot of alerts on startup?  They involve RTTI: see here for further
> description:
> http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html
>
> I've been hitting ignore all and they don't bug me after that, but I
> doubt this is a permanent solution.  I couldn't figure out what they
> meant after a few minutes on google.
>
This should now be fixed.

Leland


------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Michael Chinen]

On Sat, Jul 4, 2009 at 9:11 PM, Leland<[hidden email]> wrote:

> Michael Chinen wrote:
>> Can someone else run the mac debug build and let me know if they see a
>> lot of alerts on startup?  They involve RTTI: see here for further
>> description:
>> http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html
>>
>> I've been hitting ignore all and they don't bug me after that, but I
>> doubt this is a permanent solution.  I couldn't figure out what they
>> meant after a few minutes on google.
>>
> This should now be fixed.

Thanks Leland,

I'm waiting to find out what the 20% is going to.  RIght now I can't
launch the debugger without audacity quitting with code 45, for some
reason.  I'm hoping its due to those pop-up dialog errors.

It looks like sourceforge cvs is down now, so I'll post a verification tomorrow.

Michael

>
> Leland
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> audacity-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Michael Chinen]

On 7/5/09, Michael Chinen <[hidden email]> wrote:

> On Sat, Jul 4, 2009 at 9:11 PM, Leland<[hidden email]> wrote:
>  > Michael Chinen wrote:
>  >> Can someone else run the mac debug build and let me know if they see a
>  >> lot of alerts on startup?  They involve RTTI: see here for further
>  >> description:
>  >> http://n2.nabble.com/-Scripting-Bugfix-FindNotes--GSoC-Status-Update-(W2)-td3039112.html
>  >>
>  >> I've been hitting ignore all and they don't bug me after that, but I
>  >> doubt this is a permanent solution.  I couldn't figure out what they
>  >> meant after a few minutes on google.
>  >>
>  > This should now be fixed.
>
> Thanks Leland,
>
>  I'm waiting to find out what the 20% is going to.  RIght now I can't
>  launch the debugger without audacity quitting with code 45, for some
>  reason.  I'm hoping its due to those pop-up dialog errors.
>
>  It looks like sourceforge cvs is down now, so I'll post a verification tomorrow.

Hi Leland and all,

Thanks for making the changes.  First the good news - the changes
fixed the debug alerts.  However the idling audacity problem still
exists on my machine.  It still idles at 15-25% of my CPU, which is
higher than it should and used to be.  I wonder if it is just my
machine.  Paul, did you get that CPU usage number from a mac or PC?
I'm running mac PPC, os X 10.4, FYI.

It may be related to VST plugins that get automatically loaded,
because my console output is filled with hundreds of strings as below
that I can trace back to LoadVST.cpp :
effect: 0xd90aba0 opcode: 0 index: 10 value: 0 ptr: 0x0 opt: 0.250000
user: 0xd9108a0
effect: 0xd90aba0 opcode: 0 index: 8 value: 0 ptr: 0x0 opt: 0.039588
user: 0xd9108a0
However, this only happnes during boot.

I still cannot debug with the current xcode project to find out where
the 20% is going to- somehow xcode wasn't finding the executable
('executable path is nil!',) which is odd.  I reset the executable
path under the 'Executables' section of the project. now it quits
immediately saying
warning: Unable to read symbols for
"/Users/apple/cvscheckouts/audacity/mac/build/Debug Static/[Unknown
Bundle]" (file not found).

I'm looking into it, but if someone knows whats up, please let me know.

Michael

>
>
>  Michael
>
>
>
>  >
>  > Leland
>  >
>  >
>  > ------------------------------------------------------------------------------
>  > _______________________________________________
>  > audacity-devel mailing list
>  > [hidden email]
>  > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>  >
>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Paul Livesey]

> On 7/5/09, Michael Chinen <[hidden email]> wrote:
> Hi Leland and all,
>
> Thanks for making the changes.  First the good news - the changes
> fixed the debug alerts.  However the idling audacity problem still
> exists on my machine.  It still idles at 15-25% of my CPU, which is
> higher than it should and used to be.  I wonder if it is just my
> machine.  Paul, did you get that CPU usage number from a mac or PC?
> I'm running mac PPC, os X 10.4, FYI.
>

Hi Michael,

The CPU usage I reported was off of my build machine (8 core Intel machine
with 10Gb RAM) but it was a release build I think.

I'll set a fresh debug build going and test it on my G4 mini this evening.
 I'll report back later with the results, although debugging anything on
that machine is a chore, I may have to resort to using Rosetta on the
Intel box.

Paul.


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Leland (Audacity Team)]

On Tue, Jul 7, 2009 at 11:04 PM, Michael Chinen <[hidden email]> wrote:

I'm looking into it, but if someone knows whats up, please let me know.

One thing to try is to temporarily move the VST plugins out of their normal location so Audacity doesn't see them.  I'm guessing you're running into this:

http://landonf.bikemonkey.org/code/macosx/Tiger_PT_DENY_ATTACH.20051121020514.50199.zadder.html

Leland


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Paul Livesey]

On 8 Jul 2009, at 15:30, Paul Livesey wrote:

>> On 7/5/09, Michael Chinen <[hidden email]> wrote:
>> Hi Leland and all,
>>
>> Thanks for making the changes.  First the good news - the changes
>> fixed the debug alerts.  However the idling audacity problem still
>> exists on my machine.  It still idles at 15-25% of my CPU, which is
>> higher than it should and used to be.  I wonder if it is just my
>> machine.  Paul, did you get that CPU usage number from a mac or PC?
>> I'm running mac PPC, os X 10.4, FYI.
>>
> Hi Michael,
>
> The CPU usage I reported was off of my build machine (8 core Intel  
> machine
> with 10Gb RAM) but it was a release build I think.
>
> I'll set a fresh debug build going and test it on my G4 mini this  
> evening.
> I'll report back later with the results, although debugging anything  
> on
> that machine is a chore, I may have to resort to using Rosetta on the
> Intel box.
>
> Paul.
>

OK I made a universal debug build from CVS head and tried it out on  
two machines.

Intel box 0.8% CPU, no debug messages.  Tried it under Rosetta and it  
was pretty much the same, but a smidge higher.

G4 PPC mini, 1.0% CPU and no debug messages.

Paul.



------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Michael Chinen]

Thanks Paul and Leland.

I've moved the VST plugins folder (pluggo) and it runs idle at 3%, as
it should, like it used to before.  These plugins used to be loaded
before without taking so much CPU, so it must be due to some change.
Also, after moving the VST folder away I can debug again, which is a
huge relief!  Thanks.

Michael


On 7/8/09, Paul Livesey <[hidden email]> wrote:

>
>  On 8 Jul 2009, at 15:30, Paul Livesey wrote:
>
>  >> On 7/5/09, Michael Chinen <[hidden email]> wrote:
>  >> Hi Leland and all,
>  >>
>  >> Thanks for making the changes.  First the good news - the changes
>  >> fixed the debug alerts.  However the idling audacity problem still
>  >> exists on my machine.  It still idles at 15-25% of my CPU, which is
>  >> higher than it should and used to be.  I wonder if it is just my
>  >> machine.  Paul, did you get that CPU usage number from a mac or PC?
>  >> I'm running mac PPC, os X 10.4, FYI.
>  >>
>  > Hi Michael,
>  >
>  > The CPU usage I reported was off of my build machine (8 core Intel
>  > machine
>  > with 10Gb RAM) but it was a release build I think.
>  >
>  > I'll set a fresh debug build going and test it on my G4 mini this
>  > evening.
>  > I'll report back later with the results, although debugging anything
>  > on
>  > that machine is a chore, I may have to resort to using Rosetta on the
>  > Intel box.
>  >
>  > Paul.
>  >
>
>
> OK I made a universal debug build from CVS head and tried it out on
>  two machines.
>
>  Intel box 0.8% CPU, no debug messages.  Tried it under Rosetta and it
>  was pretty much the same, but a smidge higher.
>
>  G4 PPC mini, 1.0% CPU and no debug messages.
>
>
>  Paul.
>
>
>
>  ------------------------------------------------------------------------------
>  Enter the BlackBerry Developer Challenge
>  This is your chance to win up to $100,000 in prizes! For a limited time,
>  vendors submitting new applications to BlackBerry App World(TM) will have
>  the opportunity to enter the BlackBerry Developer Challenge. See full prize
>  details at: http://p.sf.net/sfu/Challenge
>  _______________________________________________
>  audacity-devel mailing list
>  [hidden email]
>  https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Leland (Audacity Team)]

Michael Chinen wrote:
> Thanks Paul and Leland.
>
> I've moved the VST plugins folder (pluggo) and it runs idle at 3%, as
> it should, like it used to before.  These plugins used to be loaded
> before without taking so much CPU, so it must be due to some change.

Yes, they now sport a GUI interface.  But, I removed some of those
debugging printf()s since they're really not necessary.

> Also, after moving the VST folder away I can debug again, which is a
> huge relief!  Thanks.
>
Yea, that is a pain, but you actually can leave it there and use the
kernel extension from here:

http://landonf.bikemonkey.org/code/macosx/Leopard_PT_DENY_ATTACH.20080122.html

This prevents apps from trying to disable debugging.  I've been using it
since I worked on the VST plugins as many of them don't want you trying
to disable their protections.  Unfortunately, that makes it difficult
for normal debugging that has nothing at all to do with their closed
code.

At least there's a workaround...

Leland


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel