[Thread Prev][Thread Next][Thread Index]

Flakiness in PilotManager [FIX]



Hi, guys --

	I've gotten a fair number of bug reports about PilotManager
	and have been doing what I can to fix them.
	
	It would appear that 90% of the flaky behaviour people have
	witnessed in PilotManager is because of sloppy programming
	on my part.  Right now PilotManager has an unbelievable amount
	of memory leaks stemming from a few bad function calls.
	Here's how you can avoid the problem:
	
		1.	ALWAYS quit PilotManager between syncs.  
		2.	Try to make sure that you have 50+Mb of
			swap space when you run PilotManager
			(use 'whatami' or 'swap -s' to determine this)
			
	The other 10% of the problems are because ENS sneakily 
	moves your calendar from your home machine to your server
	and doesn't tell you about it.  If things go wrong, check
	your calendar location...
			
	I'll be coming out with a new version very soon (late
	this week or early next week) which takes care of the
	memory leaks.  Until then, please try to follow the above
	instructions.
	
	If you know somebody who uses PilotManager and you suspect
	they are not on the mailing list, please encourage them to
	join this list so that they know about new versions.  This
	mailing list is my main way to track PilotManager usage.
	From the mailing list I can try to build a business case around
	why Sun really should be building a dependable, fully supported
	sync environment.
	
	Cheers,
				-Bharat
				
	
---------------------------------------------------------------------
********************************************
*   PLEASE DO NOT POST PILOTMANAGER BUGS   *
*  TO THIS ALIAS.  SUBMIT BUG REPORTS VIA  *
*     THE FEEDBACK MENU IN PILOTMANAGER    *
*             --------------------         *
*      This is a public mailing list!      *
*  Please do not publish Sun proprietary   *
*            information here!             *
********************************************


SourceForge.net Logo