> -----Original Message-----
> From: Christian Damus [mailto:community-noreply@qnx.com]
> Sent: May-01-09 1:04 PM
> To: general-ide
> Subject: RE: Slow down (4.6.0 latest)
> 
> Thanks, Mario.
> 
> I'm trying to reproduce your symptoms with 20 managed-make C++ projects
> building 80 binaries (the four standard QNX configurations in each),
> without much luck.
> 
There aren't managed make, we use our own makefile.  The project consists of a bunch of subdirectories each with a 
makefile for which there is make target.  

> I see the following on my system (IDE 4.6 RC, Ubuntu 8.10, 4GB RAM,
> Intel Centrino Duo @ 2GHz):

Same except the hardware

> 
>   - initial import of the projects into the workspace ties up the UI
>     thread for at least 10 seconds
>     -> Eclipse CDT is computing discovery info and other configuration
>         details on the UI thread, in response to Project Explorer
> refresh)
> 
>   - building all configurations of all projects doesn't make the
> workbench
>     unresponsive

For me it's after the build is complete, at least from the makefile point of view. I can see in the console that it's 
done with the actual make.

> 
>   - building doesn't cause any addr2line or c++filt processes to be
> spawned
> 
Same for me in almost every cases

>   - after build completes, I can expand a bunch of binaries in the
> explorer.
>     This makes the UI unresponsive for 1-2 seconds on each binary, but
>     this is only while the Project Explorer is waiting for details of
> the binary's
>     contents. 

For me that's instantaneous.

> Then the UI resumes as normal.  Because each
> binary-parser
>     process only lives for about 10 seconds, I don't get more than
> about
> 4
>     of them at any one time while I am expanding binaries
> 
> Do you know why so many addr2line and c++filt processes are being
> created in your IDE?

I wish I knew.

>  Are you somehow, unintentionally, triggering expansion of binaries in the Project Explorer?

I always work from the C/C++ Projects view not the project Explorer.  I never explain the Binaries "folder".  Each 
binary exist in two places, the directory the source is in and in a directory call bin that lives at the root of the 
project.

> 
> Perhaps it has something to do with the number of binaries in each
> project.  Do you have 31 different managed build configurations in each
> project?  Or, how did you configure your projects to produce more than
> one binary in a single configuration?

If I launch the make target from the root of the project it will builds all 63 executable.  But that is not what I do 
most of the time, I work on a single program at a time.

> 
> Cheers,
> 
> Christian
> 
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post28529
> 

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: May-01-09 10:24 AM
> To: general-ide
> Subject: Re: Slow down (4.6.0 latest)
> 
> Java has a lot of good debugging capabilities. Technically if we cannot
> reproduce it we may ask Mario to enable tracing for java or for
> eclipse.
> But we try to reproduce it here first.
> 
> Colin Burgess wrote:
> > You need dtrace, don't you! :-)
> >
> > Elena Laskavaia wrote:
> >> Freeze usually means garbage collection... But 30 minutes???

You read me wrong, it says it happened twice in 30 minutes, but the freeze last between 30 seconds and 60 seconds.  

> really don't know but we are investigating now
> >>
> >> Mario Charest wrote:
> >>>> -----Original Message-----
> >>>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> >>>> Sent: May-01-09 9:42 AM
> >>>> To: general-ide
> >>>> Subject: Re: Slow down (4.6.0 latest)
> >>>>
> >>>> Your project does it have lots of binaries inside?
> >>> Yes, but why is it doing it only once in a while. Since I made the
> post close to an hour ago, no problem.  Even if there are lots of
> binaries I could understand the project taking a long time to build,
> but it freeze.
> >>>
> >>>> Mario Charest wrote:
> >>>>>> With the release candidate the slow down is still there, with
> the
> >>>> same symptom
> >>>>>>  (I see lots of instances of
> >>>>>> ntox86-addr2line and  ntox86-c++filt)  However now I don't have
> to
> >>>> exit the
> >>>>>> IDE to fix the problem.  Seen it twice in about 30 minutes.
> Always
> >>>> after a
> >>>>>> build.
> >>>>>>
> >>>>> This morning I started the IDE.  Create a C++ Folder inside  a
> C++
> >>>> project (makefile), that was a mistake, I meant to create a simple
> >>>> folder, the IDE frooze for over a minute.  Then after I created a
> >>>> folder and bang, the IDE frooze for like 45 secondes and again
> same
> >>>> situation with the ntox86..
> >>>>> _______________________________________________
> >>>>> General
> >>>>> http://community.qnx.com/sf/go/post28494
> >>>>>
> >>>> _______________________________________________
> >>>> General
> >>>> http://community.qnx.com/sf/go/post28500
> >>>>
> >>> _______________________________________________
> >>> General
> >>> http://community.qnx.com/sf/go/post28502
> >>>
> >> _______________________________________________
> >> General
> >> http://community.qnx.com/sf/go/post28508
> >>
> >
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post28513
>