Mac G5 slowdowns

My Mac G5 (dual 1.8 Ghz; 1Gb RAM) suddenly became REALLY slow, especially doing three specific operations:
-- Doing a Save As in Word.
This can take 30 seconds of the spinning ball before even getting the dialogue box. Used to be instant.
-- Downloading web pages.
My broadband is fast. But pages take 15-30 seconds to download. Used to be instant.
-- Ataching a file to an email
Can take 30 seconds. Beach ball.
Things I've tried:
-- disk repair
-- permissions repair
-- zapping PRAM
-- anti-virus scan
-- uninstalling Quicksilver
-- putting iDisk Sync to Manual
-- adding 512Gb RAM (now 1Gb)
-- MacJanitor maintenance tasks
I'm getting desperate. No clue what to do next. Any suggestions gratefully received. Thanks.

Login as another User. Is it acting up there?
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
 An Apple User Group 
MacOSG Podcast >>

Similar Messages

Mac Server slowdown

Can anyone tell from these logs if something is causing our major slowdown?
Mac OS Server error log:
to repair
Apr 23 10:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 10:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 11:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 11:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 11:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 11:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 12:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 12:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 12:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 12:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 13:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 13:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 13:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 13:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 14:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 14:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 14:14:11 Xserve shutdown: halt by admin:
Apr 23 14:14:13 Xserve SystemStarter[1860]: authentication service (1887) did not complete successfully
Apr 23 14:14:13 Xserve SystemStarter[1860]: IP Failover (1893) did not complete successfully
Apr 23 14:14:17 Xserve SystemStarter[1860]: The following StartupItems failed to properly start:
Apr 23 14:17:11 localhost kernel[0]: standard timeslicing quantum is 10000 us
Apr 23 14:17:11 localhost memberd[47]: memberd starting up
Apr 23 14:17:11 localhost kernel[0]: vmpagebootstrap: 509395 free pages
Apr 23 14:17:11 localhost kernel[0]: migtable_maxdispl = 70
Apr 23 14:17:11 localhost kernel[0]: 94 prelinked modules
Apr 23 14:17:11 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Apr 23 14:17:11 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Apr 23 14:17:11 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Apr 23 14:17:11 localhost kernel[0]: DART enabled
Apr 23 14:17:11 localhost kernel[0]: Enabling ECC Error Notifications
Apr 23 14:17:11 localhost kernel[0]: FireWire (OHCI) Apple ID 42 built-in now active, GUID 001124ff fe407782; max speed s800.
Apr 23 14:17:11 localhost kernel[0]: Security auditing service present
Apr 23 14:17:11 localhost kernel[0]: BSM auditing present
Apr 23 14:17:11 localhost kernel[0]: disabled
Apr 23 14:17:11 localhost kernel[0]: rooting via boot-uuid from /chosen: A46C5BEB-0025-332C-AF80-D55B58D3C245
Apr 23 14:17:11 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Apr 23 14:17:11 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@7/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@1/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/Hitachi HDS722580VLSA80 Media/IOApplePartitionScheme/AppleHFS_Untitled2@3
Apr 23 14:17:11 localhost kernel[0]: BSD root: disk1s3, major 14, minor 4
Apr 23 14:17:11 localhost kernel[0]: hfs mount: enabling extended security on Server HD10.3
Apr 23 14:17:11 localhost DirectoryService[52]: Launched version 2.1 (v353.2)
Apr 23 14:17:11 localhost kernel[0]: Jettisoning kernel linker.
Apr 23 14:17:11 localhost mDNSResponder-107.4 (May 4 2006 16: 34:29)[37]: starting
Apr 23 14:17:11 localhost kernel[0]: Resetting IOCatalogue.
Apr 23 14:17:11 localhost lookupd[51]: lookupd (version 369.5) starting - Mon Apr 23 14:17:11 2007
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 0
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: AppleRS232Serial: 442b5020 80013020 chip base, virtual, physical
Apr 23 14:17:11 localhost kernel[0]: IOPlatformControl::registerDriver Control Driver AppleSlewClock did not supply target-value, using default
Apr 23 14:17:12 localhost kernel[0]: BCM5701Enet: Ethernet address 00:0d:93:9d:7d:a1
Apr 23 14:17:12 localhost kernel[0]: BCM5701Enet: Ethernet address 00:0d:93:9d:7d:a2
Apr 23 14:17:12 localhost watchdogtimerd: Automatic reboot timer enabled.\n
Apr 23 14:17:12 localhost diskarbitrationd[46]: disk1s3 hfs A46C5BEB-0025-332C-AF80-D55B58D3C245 Server HD10.3 /
Apr 23 14:17:12 localhost lookupd[71]: lookupd (version 369.5) starting - Mon Apr 23 14:17:12 2007
Apr 23 14:17:12 localhost kernel[0]: hfs mount: enabling extended security on Server HD10.4
Apr 23 14:17:12 localhost diskarbitrationd[46]: disk0s3 hfs E5B80404-28D2-3668-86E8-0CF43635983F Server HD10.4 /Volumes/Server HD10.4
Apr 23 14:17:13 localhost kernel[0]: ATY,BlueStar: vram [9c000000:04000000]
Apr 23 14:17:13 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Apr 23 14:17:13 localhost configd[44]: AppleTalk startup
Apr 23 14:17:13 Xserve configd[44]: setting hostname to "Xserve.local"
Apr 23 14:17:13 Xserve loginwindow[79]: Login Window Started Security Agent
Apr 23 14:17:15 Xserve mDNSResponder: Adding browse domain local.
Apr 23 14:17:16 Xserve kernel[0]: AppleBCM5701Ethernet - en0 link active, 1000-Mbit, full duplex, symmetric flow control enabled
Apr 23 14:17:18 Xserve configd[44]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Apr 23 14:17:18 Xserve configd[44]: posting notification com.apple.system.config.network_change
Apr 23 14:17:18 Xserve lookupd[91]: lookupd (version 369.5) starting - Mon Apr 23 14:17:18 2007
Apr 23 14:17:24 Xserve /usr/sbin/serialnumberd[195]: serialnumberd: Firewall rule #1 added to allow port 626.
Apr 23 14:17:28 Xserve /usr/sbin/serveradmin: servermgr_ipfilter:ipfw config:Notice:Disabled firewall
Apr 23 14:17:33 Xserve ntpdate[105]: getnetnum: "time.apple.com" invalid host number, line ignored
Apr 23 14:17:33 Xserve ntpdate[105]: no servers can be used, exiting
Apr 23 14:17:33 Xserve configd[44]: target=enable-network: disabled
Apr 23 14:17:33 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 14:17:33 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 14:17:34 Xserve configd[44]: AppleTalk startup failed, status = 92 (retrying)
Apr 23 14:17:35 Xserve ntpd_initres[245]: couldn't resolve `time.apple.com', giving up on it
Apr 23 14:17:35 Xserve configd[44]: AppleTalk startup
Apr 23 14:17:41 Xserve configd[44]: AppleTalk startup complete
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is down for SCSI Domain = 0.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is down for SCSI Domain = 1.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 0.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 1.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is active for SCSI Domain = 0.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is active for SCSI Domain = 1.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 1
Apr 23 14:18:01 Xserve kernel[0]: hfs mount: enabling extended security on RamVol
Apr 23 14:18:01 Xserve diskarbitrationd[46]: disk2s10 hfs FBF4AE84-A5B4-3901-8C4E-8369B12FB0D7 RamVol /Volumes/RamVol
Apr 23 14:18:01 Xserve kernel[0]: hfs mount: enabling extended security on JobVol
Apr 23 14:18:01 Xserve diskarbitrationd[46]: disk3s10 hfs EEABEBCD-B306-36E4-87CA-6A84907FF6FF JobVol /Volumes/JobVol
Here is the Mac OS X Windows Error log:
peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:58:42, 0] pdbods.c:odssamgetsampwnam(2329)
odssam_getsampwnam: [0]getsam_recordattributes dsRecTypeStandard:Users no account for 'donh'!
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 14:17:18, 0] /SourceCache/samba/samba-100.4/samba/source/smbd/server.c:main(789)
smbd version 3.0.10 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004

Hi
Add a DNS record using the relevant DNS snap in tool on the AD Server for the mac server as it should improve server and network performance. OSX and especially OSX Server is absolutely dependent on a properly configured and tested DNS Service running somewhere. Apple recommend it as good practice even if you are just running simple file services like AFP.

Mac mini slowdown when downloading

I have a brand new Mac Mini Core i5 2.3 GHz with ML 10.8.1 installed and it seems like everytime I have a few fullscreen windows open and I download something the system slows to a crawl!
Anyway else experience this and how did you fix it?
Thanks!

I have a brand new Mac Mini Core i5 2.3 GHz with ML 10.8.1 installed and it seems like everytime I have a few fullscreen windows open and I download something the system slows to a crawl!
Anyway else experience this and how did you fix it?
Thanks!

Mac Flash slowdown

Recently all flash has been playing super slow on one of my
Mac (G4 800mhz) This seems out of the blue, no recent installations
etc.. same old stuff, but now flash plays at a crawl in all
browsers. Any suggestions on how I can fix this??

how much ram do you have & how much ram does your
graphics card have ?
mostly all adobe products need more graphic card ram , then
they do system ram
except for After Effects all the other video authoring
programs

Attn: ALL APPLE PORTABLE OWNERS -Macbook Pro, MacBook Air Apple portable slowdown / kernel high CPU solution

Attn: ALL APPLE PORTABLE OWNERS -MacBook Pro, MacBook Air, Mac mini slowdown kernel / high CPU use problem and solution.
YOU COULD FRY YOUR COMPUTER IF YOU DO NOT FIX THIS PROBLEM SO PLEASE READ THIS ENTIRE MESSAGE!
YOUR MAC WILL THANK YOU
Hey all.
Like many of you I've got a newer Apple portable which slows down to an unusable level for an unknown reason. In my case a 13" mid 2009 Intel MacBook Pro Core 2 duo laptop. After many failed attempts to figure out what this nutty problem is I have discovered the problem, the solution and I have solved this for my own MacBook Pro. Since this fix it has been working immediately and consistently -without issue
I am sharing this with you in hopes that you to can fix your Apple portable yourself or so you know what to tell the Apple techs so they can quickly fix your Mac from this wacky and unfortunate kernel CPU hogging problem.
User Software Symptoms :
Your Apple portable computer periodically for an unknown reason slows down making everything frustratingly slow. This happens even when running previous apps that were never a problem; things that your Mac should be able to handle easily but for some reason now it can't.
Slowdown most often happens during high CPU use such as gaming, video playback/editing, etc. or when running multiple apps (even non CPU intensive apps) at the same time.
Possible Hardware Symptoms:
Your computer is making more noise than it did previously.
Your computer occasionally makes more noise but then gets quieter.
Your computer is always extremely quiet (too quiet) even during high CPU apps -worst case scenario.
It feels hotter than it normally does. Test: After several minutes of the slowness/high kernel CPU touch the computer to feel if it's hotter than normal.
Looking at Activity Monitor (in the Utilities folder) shows the kernel_task is going bonkers eating up CPU but you have no idea why.
After trying many different things to solve this problem such as :
PR ram reset, SMC reset, fresh OS install of 10.5 and 10.6 on external hard-drives, calling and speaking to various Apple tech people who had no ideas/solutions, etc. I had no luck.
Btw, if you're having the symptoms I've decscribed above I would not run the Apple Hardware check (read below as to why). You could fry your Mac!
After much testing I found the problem :
It is my belief that "recent" Apple portable computers are using low quality internal fans which soon stop working!
Fail time period seems to be about 1.0 years to 2.5 years of use but this fail rate could vary depending on use.
First noticeable symptoms (depending on what you notice) could be computer slowdown or your fan is making more noise than it normally does. This is your fan's lubrication slowly eroding making your fan spin slower and less smooth resulting in the louder noise and slower rpm spin speed. The slower fan spin speed means less cooling is happening for your computer. The effect on your computer is that the CPU and other chips are heating up! Overheating to be more specific. When your computer's chips overheat they get wonky and screw things up. Most often this seems to have the effect of making the kernel hog CPU resulting in a frustratingly slow user experience! Heat kills computer chips and it is extremely bad for them. Extreme overheat or repeated overheating has been said to shorten the life of computer chips or in extreme cases even fry them completely!
The longer this goes on without being fixed your fan loses more lubrication and spins slower and slower cooling lesser and lesser resulting in your CPU heating up more and more possibly shortening the life of your Mac! Eventually your fan will stop completely and you could fry your chips! My fan stopped completely and my MBP was running very quietly, too quietly. Luckily I did not fry my chips because I was avoiding using high CPU apps because I knew something was wrong due to the massive slow down and wonkiness when I'd run them.
Side Note:I'm a bit concerned about all those Mac mini servers which may be using the same defective low quality fans which cannot be easily serviced by their owners as they are co-located in some server facility. One positive thing is those facilities are usually well airconditioned keeping temps low.
I suggest you do not run the Apple hardware test if you suspect your computer is overheating because the hardware test can seriously heat up your Mac! I tried running this test and my Mac got so hot I had to shut it down forcefully and I was concerned I damaged the chips. If you want to run the Apple hardware check make sure your CPU temperature is ok and that your fan works well before you run the test.
IF YOU DON'T FIX THIS PROBLEM YOU COULD FRY YOUR COMPUTER DUE TO HEAT DAMAGE!
DO NOT IGNORE THIS PROBLEM YOUR MACS LIFE MAY DEPEND ON IT!
First you need to properly diagnose this problem and see if your CPU is getting to hot and you need to see if your fans are spinning at high rpms giving proper cooling, or if they are spinning at low rpms when running high intensive apps as your CPU temp increases.
TEST IF YOUR FAN(s) IS WORKING CORRECTLY :
Unfortunately Apple does not include CPU temperature reading software nor fan rpm speed software that I am aware of.
However, There are two free ways that I know of to check your CPU tempurature and your fan speed :
One app shows fan speed, and CPU heat, etc.
One app shows fan speed, CPU heat and allows you to adjust your fan speed settings.
One app is a dashboard widget, the other is a system preference.
I suggest you download both of these to check your computer statistics.
http://www.eidac.de/?p=134
http://www.islayer.com/apps/istatpro/
http://fan-control.en.softonic.com/mac
I am not exactly sure what proper CPU temperatures are for the different Apple computers and this will change given different CPU loads.
My MBP doesn't seem to function properly with anything around 90 degrees or higher (celcius).
It seems when the fan is operating normally the CPU temp should not stay above 78 degrees even under heavy load, at least with the apps I'm running in the room temperature I'm in.
I can post back later with more specific temps under longer load, etc. but I wanted to get this post up for people to read as soon as possible so they don't fry their Macs.
If a bad fan is your problem :
THERE ARE ONLY TWO SOLUTIONS FOR THIS PROBLEM :
Fix or replace your fan so it cools the CPU and other chips properly.
I fixed my fan myself and I didn't need to buy a new one. Total cost was about $8.00 because I had to buy a #00 sized screwdriver and had it shipped to me. Price includes shipping.
On my mid 2009 model MacBook Pro fixing the fan was incredibly easy :
Before I started doing this I wasn't 100% this was the problem so I decided to try to fix my fan instead of ordering a new one and replacing it. As it turns out I didn't need a new fan, I only needed to clean the existing fan and relube it's axl so it could spin easier like when it was new. It also didn't make sense to buy a brand new fan from an Apple authorized parts reseller selling me the same low quality fan for $49.00 which would probably fail in 2 years again. Prices for new comparable fans from different manufactures range from about $15.00 USD + shipping to around $49.00 USD + shipping depending on where you order them from and what brand you get.
How to fix / replace your internal fan on a mid 2009 MacBook Pro :
Please note : I am not a hardware technician, nor expert. If you decide to fix your Mac yourself you do so at your own risk through no fault of my own. Prior to opening up your Mac you should google around and learn how to do it correctly and safely so you won't damage your Mac. For example, it is possible for you to damage your Mac by static electricity from your body. To avoid this I believe proper procedure is that you wear a 'ground strap' (around your wrist) which you clip to your Mac's metal body so your body will not excude a charge into your Mac. I believe the idea here is to keep your body's charge level and your Mac's similar. Since I do not have a ground strap and fixing/replacing the fan doesn't require touching any chips I did not wear a ground strap during my fan fix. What I did was periodically repeatedly touch the metal case of my MBP hoping that would be enough and it was. Avoid unecessary actions that can build up a static charge in you. Once I started the repair I did not walk around the room building up an electrical charge in my body. Walking on carpet can often build up a large charge in us so it is better to be avoided while working on your Mac. Certain clothing can build up static charges. Combing hair, etc. If you need to get up from your repair when you come back make sure you first touch the Mac's metal case and not anything inside.
Now that we're done with the scary paranoia, below you will find some instructions on how I fixed my MBP's internal fan
Before you begin:
Check out someone's video (not mine) on how to remove / replace the fan (but not take it apart and repair it):
http://www.youtube.com/watch?v=AghE9newvbs
Check out someone's web page (not mine) on how to replace the fan in a mid 2009 MacBook Pro:
http://www.ifixit.com/Guide/Installing-MacBook-Pro-13-Inch-Unibody-Mid-2009-Fan/ 1338/1
How to repair your mid 2009 MacBook Pro fan:
Make sure you are in a 'secure' environment. No pets, no kids running around, no drinks near the Mac, etc.
Make sure your computer is unplugged from it's power supply and turned off. NOT slept. Totally off / powered down.
1. Get a size #00 phillips screwdriver (Hobby store, Radioshack, Amazon).
2. Open up your MBP by unscrewing the bottom (yes flip it over so it's resting upsidedown). Note where each screw goes because some are different lengths. I placed each one around my MBP where they go, insuring I know their order (don't jumble them up). Note which direction your MBP is facing when it's upside down so if you spin it around while working on it you still know where the screws go.
2b. Some recommend removing the MBP's battery but I didn't do this step. You probably should, just to be safe. Follow the online instructions from the web page I listed about disconnecting the battery.
3. Unscrew the fan's 3 holding screws.
4. Unplug the fan's electrical connection (lift it straight up off the board). If you need to you can try to pry it up while you lift with a non metal/non electrical conductive object like a spudger if you have one or -perhaps a pen cap. Before you remove it, look closely at how it's attached so when you put it back on you won't wonder if you're doing it correctly. There's only one way it can go because it cannot fit 'the wrong way' but looking at it closely will make you feel more confident popping it back on when the time comes.
5. Remove the fan - it easily lifts out.
6. Take the fan apart by unscrewing it's one screw then unlatching the plastic clips which hold it together.
7. Seperate the fan blades from the housing. Lift the fan blades off of the fan housing by pulling it straight out away from the housing.
8. Clean off the dust that's gathered. A can of compressed air helps here (I didn't have one). I used a little brush from my electric shaver kit which worked well. Once you've removed all the dust from the fan and surrounding areas proceed to the next step.
9. Reapply new lubrication. You need less than 1 drop. Be sure it covers the entire fan blade axl as this is what needs to be well lubricated. Make sure there isn't excess oil that will fly around when the axl/fan spins at high rpms. I used the only oil I had which was olive oil (for cooking!) but I do not suggest this. At the time I was doing this I didn't know my fan was the problem so I wasn't even sure I was going to relube it. You should probably use something more appropriate perhaps like 3 in 1 oil. A good idea would be to call the manufatures of these little fans and ask them. Maybe a hobby store knows of good lubricants for these purposes?
DO NOT use things like WD 40 as it's not a long term lubricant or so I've read.
10. Once your fan is now clean and oiled (make sure there isn't too much oil) reassmble the fan.
Push the fan blades/axl back into the housing shaft. Give it a few spins with your finger.
Screw together the fan housing then reclip the clips.
11. Place the now reassembled fan back into your Mac and screw it in place (3 screws).
12. Reattach the fan's electrical wiring by gently pushing it into place. Make sure you've got the right end facing down before you push it in place.
13. Once your Mac's internals are clean and reassembled, place the rear cover back on your Mac and screw it in place.
14. Double check you didn't forget anything like screws, tools, etc.
15. Boot up your Mac and monitor the temperature and fan speed using those programs.
Compare the previous temps/fan speed to the current temp/fan speed.
Run a high CPU intensive app where your computer has been slowing down.
You should now have a happy Mac
If you have this problem and this solution fixed it for you please post in this thread letting me and everyone else know!
Hope that helps.

Thanks for your lengthy reminder dude, I have a similar Mac with yours. I suspect its a software fault because it happens after I upgraded to Lion, 10.7.2.

How to identify damaged files in ext HDD?

Early 2008 iMac - iMac8,1 - Intel Core 2 Duo - OS X 10.6.8 - (int) Samsung SSD 840 EVO 500GB - (ext) OWC Qx2 enclosure w. 4x2TB TOSHIBA DT01ACA200 - Wacom Intuos Pen&Touch tablet (no mouse) - DSL - Flash Player.
I think hardware is the place for this question.
I inherited this iMac back in May/June, spent a month or two with it, did a fresh install of Leopard, and then Snow Leopard on top of that. Everything seemed fine. Speedy response. Decent browsing speed, even with my crappy 3 Mbps DSL.
I added two separate HW upgrades: a SSD int hard drive + RAM to 4GB (installed by reputable local shop), and added a 4-bay ext HDD set up as 4 independent drives, JBOD (purchased from OWC). I feel I made a mistake in doing both of those things at the same time, as I immediately encountered glitches that have been hard to troubleshoot. The worst was the ext HDD / enclosure suddenly un-mounting all by itself, complete with error message ("was not ejected properly"), promptly after which the drives reappear on the desktop, with their contents seemingly in place.
I'm not looking for help troubleshooting; I think I've found the problem, at least for the un-mount issue (bad FW port, thankfully there are two). There might or might not be lingering stall-when-opening-folder issues, too soon to tell. Both vendors have been helpful with their responses.
What I'd like to know is how (or if) the contents of the ext HDDs can be scrutinized for damage? This un-mount thing happened at least a dozen times, and several other times I was forced to manually shut down the HDD enclosure when everything else was frozen. I have to think something's been corrupted or damaged with all of that un-ejected off-and-on activity.
Any input is appreciated. Thanks in advance!

Old Toad wrote:
Have you run any cleaning or optimizing apps like MacKeeper or CleanMyMac? Those are known to cause serious problem with Macs including slowdowns,
No, I've always avoided those like the plague. The pop-up ads for that crap are the obvious cues to stay away!
Linc Davis wrote:
The only meaningful test of whether there are "corrupt files" is to use the computer. If it behaves normally, you can assume that the operating system and applications are intact. As for your other files, open the most important of them and see whether the contents are what you expect.
Though swapping the FW port SEEMS to have stopped the sudden un-mounting (maybe not enough time spent scrutinizing that yet), there is still problematic behavior. Just this evening, after the desktop was on all day but saw little use (Safari, iTunes), I tried simply opening one of the hard drives:
- 8 minutes to simply open the window. Spinning beach ball. Window changed dimensions from prior use, appeared as though it was opened for the first time. It showed no contents.
- 20 more minutes to show contents. During this time, the spinning progress wheel spun. Contents finally showed up.
- 8 more minutes to open one folder. Spinning progress wheel.
Contents appear to be there. This is a storage disc, no backups ever performed. This new 2TB drive contains only 100GB.
This stall seemingly caused other stalls elsewhere. Namely, a simple text copy-and-paste function in TextEdit. When the HDD finally decided to finish, TextEdit was available to me again.
Welcome to my world.

Cannot publish: solution found

Hi all. I'm an iWeb/.mac newbie with a trial .Mac account testing whether or not to keep the .mac.
I first fired up iWeb a few weeks ago, then didn't have time to mess with it. Recently, from lack of time to do a photo gallery myself via emacs, and the need to share some pictures, I used iPhoto to put some pictures online on the .mac account.
That worked fine and page was created, that is until I started messing with iWeb trying to add more pages. I had previously published one small/test page just fine, then continuously (weeks) had problems and could not publish. Then 1.1.1 came out, and I still could not publish.
Some of the solutions I tried: editting the Domains.sites package. Deleting the iweb prefs file. Deleting the Domains.sites file. (see group archive for explanations of these methods)
Nothing worked, and I spent hours reading all your helpful messages in this forum and surfing for solutions.
Last nite I finally hit on the problem - an upstream httpd proxy server (squid, on a Firewall). I realized the first iWeb page I had published I did from a Mac at work. The rest I tried doing from home, where the proxy server is. Whenever I tried to publish from home I got the "cannot publish" error. I had mistaken that for .Mac downtime, slowdowns, phase of the moon, you know the drill.
So last nite I turned of the web-proxy here, and lo and behold I now have absolutely no problems publishing (proof: http://web.mac.com/lottadot/ )

With the firewall I'm using it's just a checkbox to enable/disable. YMMV. BTW, Astaro is free for home use. http://astaro.com/

My SUID File has apparently been changed, what does that mean? Seems to affect my speed.

My SUID file, whatever that is , has been changed and is not fixed when I use Disc utilities to correct permissions. seem to be slowing things down.

That change is not the issue, does not need "fixing", and is not the source of your slowdowns. If it were a real issue, Apple would be providing a fix for it every time (else the genius Bar would be swamped with visits to fix that).
Please describe the SYMPTOMS you see in the greatest detail you can so that others can help you determine exactly what might be happening to your Mac. Slowdowns happen for dozens of different reasons.

Mac Mini Mid 2011 General system slowdown when transferring files?

Hi i have a stock mac mini mid 2011, 2.5ghz i5, 4gb ram, 500gb HDD os 10.7.1 and i've noticed a general system slowdown when transferring files on 10.7 and the last 10.7.1 update ( from usb to hdd, another computer on my local network to the mini, external dvd to the mini, etc).
I could describe the slowdown as mouse pointer movement suffers, its "laggy", application take longer to start, even menus in them from appearing, writting something on the keyboard i have to wait like 5 - 10 seconds so the words start appearing in the app (i.e. textedit).
I wanted to know if any other new mac mini owner has had this issue and if there is any solution to this(that would not involve buying a SSD for example)?
Im not really sure if this is a hardware or system issue but it really is getting on my nerves(i know i could just wait for the files to transfer which is what i do now but i dont think that should be), since i also have a old macbook from 2007 2.0ghz c2d, 2gb ram, 250gb HDD os 10.6.8 and have never had this problem before.
Thanks in advanced.
Let me know if i need to give more info on this subject.
Edit: I forgot to mention, the funny thing is doing a time machine backup to my external HDD or transferring files from my HDD to a usb doesnt give me any kind of slowdown.

Hi Rick, I'd see if it's reated to this, which has many symptoms...
Try this: "sudo pmset autopoweroff 0" and "sudo pmset standby 0"
http://xlr8yourmac.com/archives/sep13/091313.html#10.8.5SleepEjectTip

Bridge CS3 slowdown, upgrade to 5 or 6 on Mac?

My OSX is 10.8.4 and I use PSE10 for mac with Bridge CS3. Recently, I have observed a major slowdown in bridge and some annoying interactions with PSE10. I have about 17,000 jpegs (of insects) organized in hierarchical folders, i.e., taxonomically. I have 4 GB of memory, recently installed.
1) It now takes several seconds to scroll down through the images in any folder.
2) Often, when I shift-click to highlight files (to move or rename them), PSE10 opens the files when I don't want it to. Very annoying. I have taken to waiting for a full second or two before I do anything.
3) Bridge also crashes frequently, at least once a day, and I use it every day.
OK, would upgrading to Bridge CS5 or 6 fix this problem? Or is this a system thing? And would Bridge CS5 or 6 work with PSE10?

I agree with Curt,
in addition to his post:
OK, would upgrading to Bridge CS5 or 6 fix this problem? Or is this a system thing? And would Bridge CS5 or 6 work with PSE10?
Bridge is designed for use with Creative Suite applications an PS elements is not part of the Creative Suite or the Creative Cloud. It might be possible to use Bridge with PSE for opening files in but the advantage of using start up scripts for Photoshop is not available for PS elements.
I believe PSE 8 for Mac is the only version of PSE that came with Bridge (version 3, part of CS4) so that might be a route for you to follow as the cheapest option.
Also every new version of Bridge needs a new cache for all the files. (not a big deal but it takes some time with all your files. You have to select the main folder and use 'show items from subfolders' and then let it run overnight to recache again.
Can you specify what computer you are using. While the minimum required RAM is still advertised as 1 GB you certainly will gain from putting as much RAM as possible in your machine.

New Mac User Facing Sudden System Slowdowns - Advice Appreciated

I recently purchased a MacPro for video editing, switching from Premiere on my PC.
Everything was working great for the past month, and now suddenly I've been having terrible slowdowns in Final Cut Pro. Shortly after these slowdowns occured (constant dropped frames), I tried to restart the system and received a black screen with messages:
exited abnormally, bad system call;
respawning too quickly; throttling
I restarted, and this time the computer seemed to start up normally, but I'm still experiencing the slow performance and the dropped frames in Final Cut.
I'm fairly adept at solving performance issues in a WinXP environment, but am very new to this.
If someone could give me some troubleshooting info, I'd greatly appreciate it. Could this be a RAM issue? I did purchase extra RAM from a third party to up my total from 1 GB to 3 GB shortly after I purchased the Mac Pro. I'm also using an ATI X1900 graphics card purchased through Apple.
The only thing I have done to the system over the last couple days before this happened was download a couple free plug-ins for Final Cut and connect the Mac to the internet through an ethernet cable coming from the same router that is attached to my PC.
Again, any help, general or specific, would be greatly appreciated.

I use Final Cut Express and I wouldn't have installed the "free" plugins at all. Best advice: remove them and reinstall Final Cut Pro over your current installation of Final Cut Pro. I'm assuming here you are using the latest universal release of FCP.
As far as I know there are no or few universal plugins. And more importantly I know of no "free" universal plugins.
Tim...
3Ghz Mac Pro w/4GRam, 1500GHD/ 13" BlackBook, Black iPod - ALL fullly loaded Mac OS X (10.4.8) 30" Cinema, HPColorLJ Printer, LaCie 600Gig External & LaCie DVDRW/CDRW Drives

*** FOUND and SOLVED: Flash Player/Mac slowdown*** DO NOT return your iMacs

Fellow Apple enthusiasts,
Sorry for the multiple posts, but I want to get this info out as soon as possible. I've found the cause of the infamous Mac "slowdown." I haven't seen this information posted anywhere yet, and hope to introduce a PROVEN solution to alleviate some frustrations with many Mac users out there. Don't return your iMac! Your hardware is fine. It is an Apple software issue that should be easily remedied with an update.
I'm posting this here in the iMac section first, because many seem to believe that only the iMac is affected. This is false. It will probably affect any Snow Leopard machine, but the iMacs are the first Macs to come with the Wireless Mouse drivers pre-installed alongside the Magic Mouse.
THE PROBLEM: Resource leakage, system slowdown, and slow/choppy Flash video playback while pegging CPU utilization for Flash Player, as observed in the Activity Monitor.
THE CAUSE: MAGIC MOUSE drivers. Yes, the Wireless Mouse update is the cause. With the update installed, the problem will occur as long as the mouse is paired with the Mac.
It will occur REGARDLESS if:
- The Magic Mouse is in standby mode
- The mouse is switched off via power switch underneath
- The mouse is disconnected under the Bluetooth drop down menu at top of screen
The reason I'm reporting the Wireless Mouse Update as the culprit is:
I have a 13" unibody MacBook Pro (Early 2009) and purchased a Magic Mouse online. Received it yesterday - Monday, November 2nd, and updated the Wireless Mouse driver files via Software Update under the Apple menu.
After the update, I noticed the same Flash Player problems mentioned online, and indeed, System Monitor showed about 104% utilization. Flash videos appeared to be running with 1/2 to 1/3 frame rates.
* THE SOLUTION: Remove your Magic Mouse using the Bluetooth Utility.
- Click on the Bluetooth icon at top of screen, and choose "Open Bluetooth Preferences." Or, use equivalent steps via System Prefs.
- Highlight the Magic Mouse, and then click on the "-" minus at the bottom of the window.
- Your Magic Mouse will no longer function with your Mac, obviously. Use a different mouse to avoid the problems you've experienced.
- The Flash video problem will no longer occur, and suspect the resource leakage may cease as well.
A restart may or may not be necessary, but upon restarting my MBP, Flash video playback returned to normal, with about 40% utilization while streaming a single Flash video.
The steps above are simply what I used to rectify the problem. I don't know if other bluetooth mice will cause this problem. I have not tested any other wired or wireless mice either.
I'm just an average user who experienced and recognized the Flash video playback issue on my system. Upon seeing the problem occur, I simply reversed the last change I made to my computer, and found that this solved the problem. Both the problem and the fix are repeatable. The information here has been reported to Apple.
DON'T RETURN YOUR COMPUTERS! I'm confident that once Apple is aware, a software fix will be made. Again, this will probably occur on any machine running Snow Leopard, and may be even more widespread. I will continue conversation with Apple on this subject.
Good luck to us all in resolving this issue as quickly and easily as possible.

Posting here won't get Apple's attention. File a bug report with Apple if you want it to fix the issue. To do ths, join the Apple Developer Connection (ADC)—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report. The nice thing with this procedur is that you get a response and a follow-up number; thus, starting a dialog with engineering about the issue.

Problem with mdworker process, mac slowdowns

Hello. I have been having slowdowns of my mac without a reason.
The problem that seems to be responsible is mdworker, as in the console about the only messages i get are phrased like this:
"07/12/14 16:26:06,000 kernel[0]: Sandbox: mdworker(20160) deny mach-lookup com.apple.audio.audiohald"
I have about 5 or 6 of these per second, practically filling up the whole console.
I have no audio apps running in the background, no external soundcard plugged in, nothing. Basically the computer is idling and still presenting all these problems.
Sometimes a couple of these messages pop up:
"07/12/14 16:27:59,973 sandboxd[972]: ([20160]) mdworker(20160) deny mach-lookup com.apple.audio.audiohald (pre-plugin fstype:hfs fsflag:480D000 flags:240000005E diag:0 isXCode:0 uti:public.data plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 2483218)"
Doing sudo mdutil -t 2483218 in the terminal returns this string:
/Users/Polygon/Library/Application Support/Google/Chrome/Default/QuotaManager
which is weird because i killed all chrome-related processes in Activity Monitor before.
Any of you have any idea what could cause this?
Thanks,
Luke

Mdworker is part of Spotlight Indexing: http://osxdaily.com/2009/09/14/mdworker-what-is-mdworker/
If you think it's an issue for you, just Google "mdworker" and follow some of the many suggestions.

Major Mac slowdown. Common?

I have a 12' PB G4 with 80 gigs (46 free) and 768 ram. I play a fairly visually demanding game called World of Warcraft. When I first purchased my Mac, the game ran flawlessly at 35-100 Frames per second and was very, very smooth; now however it runs at 1.5 Frames per second -17 Frames per second.
I don't know if anyone here has ever seen a game run at that speed, but it looks like a series of similar pictures joined together in succesion.
I've had the computer since July, i download a decent amount of videos on it, and record music on it periodically, but i was wondering what may have caused this immense slowdown.
I realised that it wasnt Hard drive space, i have over half of the space free. So i moved to my activity monitor and saw what was taking up RAM.
On the list of things taking up RAM there is some normal things such as Safari, Itunes, you know the regular apple stuff; then there is some that i have no clue what they are taking up up to 150mb Virtual memory.
So i have 2 questions.
1.) What are these processes: "PBS" -54.18 Virtual memory, "Login Window" 130.70mb Virtual memory, "ATSSERVER" 56.11mb Virtual memory, "Speech syn.." 101.99mb Virtual memory....etc.
What are those processes? In downloading videos from Limewire did i aquire any Spyware or adware that would be slowing my comp down?
2.) If these arent any issue with slowing down a computer 300% of its original speed, what could it be? any ideas? The reason i bought a Mac was so that it wouldnt slow down like i was told it wouldnt...compared to a Windows machine..Please, please, please help.

First welcome to the discussions.
http://discussions.apple.com/thread.jspa?messageID=607640&#607640
See if this helps.
Don

System slowdown after install of Mac OS X 10.6.8

My MacBook Pro 13" after installing Mac OS X 10.6.8 update it's so slow in all, the apps are opening slower than the 10.6.7, and the shutdown takes about 1-5 min.
Please, help me!

Sort of normal for first boot or two. And always see identical comments after each and every OS update.
But you did not post in a forum for notebooks or for general OS X.
Snow Leopard
MacBook Pro
MacBook Pro Apple Support
There are some tips for what to do before applying updates, and how to insure you have a good safe upgrade. Even whether there are some 3rd party apps to beware of.

Mac G5 slowdowns

Similar Messages

Maybe you are looking for