[chandler-users] Annoying modality bug with "Purging..." and "Tip..." dialog

[William K. Volkman]

Hi Mimi,
On Mon, 2008-07-21 at 17:37, Mimi Yin wrote:
> For what it's worth. This will hopefully be less of an issue in the  
> next release as we have now replaced the "Purge" functionality with a  
> weekly auto-reload. So the Purge dialog will no longer pop up by itself.

Umm...that sounds like it is going to make Chandler less usable for
people with large collections.  The purge removed ~5K items from my
collection.  I've not done any timing tests but usually creating entries
takes longer than purging the dead tuples.

That said I'm kinda curious, I've not added any entries today, busy
taking off some ones that have "heft".  I've worked on 6-8 of them today
and just performed a "Compact" and it says it removed 377 objects and 8
lucene documents.  The item to entry ratio seems a bit on the high side.
I'm also guessing it re-indexes the document which seems a bit like
unnecessary overhead as I know I didn't change that many of them, mostly
set the triage status to "done".

I just did it again, I haven't modified anything, only popped the window
to the foreground to look at it. Chandler reports it purged 78 items, 99
values, 127 refs, 65 index entries and 1 lucene document.  There
probably was a background "Sync" operation performed however nothing
changed.

HTH,
William.

> 
> Not getting at the root of the problem, but will hopefully mean it is  
> less likely for anyone to run into this problem.
> 
> Mimi
> 
> On Jul 21, 2008, at 4:30 PM, Jeffrey Harris wrote:
> 
> > Hi William,
> >
> >> 	When I started Chandler 0.7.7 today it issued a grab for the  
> >> mouse and
> >> then wouldn't respond.  I had to login from another system to kill
> >> chandler to be able to get back my system.  I let the "Tip of the  
> >> Day"
> >> display and it had popped up, then the "Purging Obsolete Data in nn
> >> seconds" dialog popped up.  At which point I could not click on  
> >> anything
> >> to get the system to respond.  I watched and waited while it count  
> >> down
> >> the seconds and then purged the data.  After completing that it still
> >> wouldn't let me click on anything.  Now application modal is bad  
> >> enough
> >> however it appears that it is using system modal because I  
> >> couldn't even
> >> get to any of my other windows.  I would recommend that you remove
> >> modality from the "Tip..." dialog (if there is any) and make sure  
> >> that
> >> all dialogs that can come up are only application modal (if  
> >> necessary)
> >> and not system modal.
> >> Thank you,
> >> William.
> >> Platform: Linux Fedora 7 displaying to a Linux Fedora Core 2
> >> workstation.
> >
> > I don't think wx offers a dialog that's modal for all applications,  
> > but that dialog is modal within Chandler.
> >
> > Once in a great while I see something like this when starting  
> > Chandler.  Basically the CPU gets pegged and UI is blocked for 2-3  
> > minutes.  When the CPU is pegged, it often appears to me that the  
> > whole system has stopped responding, but it's just slowed to a  
> > crawl.  I've always gotten the UI to respond again eventually (if I  
> > walk away and come back later), but that's not much comfort, I know.
> >
> > We would LOVE it if you found a way to reliably reproduce the  
> > problem, since debugging an infrequent but deeply irritating bug  
> > like this is really hard.
> >
> > Sincerely,
> > Jeffrey
> > _______________________________________________
> > chandler-users mailing list
> > chandler-users at osafoundation.org
> > http://lists.osafoundation.org/mailman/listinfo/chandler-users