On 02/24/10 02:30 PM, Haik Aftandilian wrote:
I'm running build 132 from the /dev repo on a dual core P8400 2.26GHz
with 2GB of RAM and my system became slow and then almost totally
unresponsive while the pm-checkforupdates script was running. It seemed
like all applications' memory had been paged to disk because I could
hear the disk running and the desktop environment was very
slow--unresponsive to keyboard commands and very slow to switch windows.
prstat showed the process CPU utilization was over 30%. I used mdb to
save a core file which turned out to be 622M in size. I've attached the
stack trace. Does this sound like a known bug? I didn't see a release
note about it. Would more information be needed beyond the stack trace?
If you're on build132, then the update check for newer builds (133+) is
very expensive. This is a known issue. Once you upgrade to build133,
you'll see the memory usage drop significantly for future update checks.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
