RE: [mylar-dev] this week's plan (v0.3.9)

["Mik Kersten" <beatmik@xxxxxxx>]

Although active search can be 'dangerous' if you put your degree of
separation out to 5 for the Java parts, Eclipse freezing for any amount of
time is unacceptable and a bug.  I keep my degree of separation at 2 or 3
depending on how much context I have, and there is no noticeable memory or
performance issue.

So did you put your degree of separation out to "workspace"?  Could you
report this as a bug?  Perhaps there should be a safeguard, since Mylar
knows when it's about to run an overly large amount of searches and could
stop warn you...

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: September 19, 2005 8:15 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] this week's plan (v0.3.9)
> 
> Mik Kersten wrote:
> 
> > Mylar 0.3.8 is now available and provides the first cut at predicted
> > interest facilities such as Active Search (new & noteworthy snippets are
> > below).  These features are available for those users who update and are
> > in Phase 2 of the user study (under Preferences -> Mylar -> User Study
> > must have over 25000 events).  If you should be in Phase 2 but don't see
> > the Phase 2 update site email mylar@xxxxxxxxx <mailto:mylar@xxxxxxxxx>.
> >  The focus for this week is refactoring awareness and continuing to
> > de-couple the UBC study.  Special thanks goes out to Brian de Alwis for
> > identifying some important Linux/GTK issues.
> 
>    It seems that active search can be quite dangerous. When I was trying
> to change some properties from a drop-down toolbar buttons it make
> entire Eclipse workbench to freeze for about 5 minutes (huge amount of
> memory were allocated during that time)... :-(
> 
>    regards,
>    Eugene
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev