Skip navigation

Intermittent spinning wheel, mdworker and CrashReport processes in Activity Monitor

1034 Views 5 Replies Latest reply: Jan 8, 2013 1:57 AM by japamac RSS
h2oneuron Calculating status...
Currently Being Moderated
Jan 5, 2013 4:57 AM

It started with spinning wheel, not knowing what was bogging the system down followed by the grey screen with the flashing ? folder and a couple of Kernel Panic crashes. After using the Step by Step guide (https://discussions.apple.com/docs/DOC-3353) and OnyX, it appears that I have "fixed" the boot problem.

 

"Fixed".

 

I still have the spinning wheel issue, albeit intermittently. During these spinning wheel lags, I have looked at the Activity monitor and have seen mdworker and CrashReport gobbling up %CPU.

 

In the console, it appears that CrashReport is generating a ton of logs (hundreds in the last hour) regarding mdworker that look like this:

 

Jan  5 07:38:41 Ricks-MacBook-Pro.local ReportCrash[2882]: Removing excessive log: file://localhost/Users/ricksmith/Library/Logs/DiagnosticReports/mdworker32_2013 -01-05-073725_Ricks-MacBook-Pro.crash

Jan  5 07:38:46 Ricks-MacBook-Pro com.apple.launchd.peruser.501[152] (com.apple.mdworker.32bit.01000000-0000-0000-0000-000000000000[2908]): Job appears to have crashed: Segmentation fault: 11

Jan  5 07:38:46 Ricks-MacBook-Pro.local ReportCrash[2909]: Saved crash report for mdworker32[2908] version 707.3 to /Users/ricksmith/Library/Logs/DiagnosticReports/mdworker32_2013-01-05-073846_Ri cks-MacBook-Pro.crash

Jan  5 07:38:46 Ricks-MacBook-Pro.local ReportCrash[2909]: Removing excessive log: file://localhost/Users/ricksmith/Library/Logs/DiagnosticReports/mdworker32_2013 -01-05-073730-1_Ricks-MacBook-Pro.crash

Jan  5 07:38:46 Ricks-MacBook-Pro com.apple.launchd.peruser.501[152] (com.apple.mdworker.32bit.01000000-0000-0000-0000-000000000000[2910]): Job appears to have crashed: Segmentation fault: 11

Jan  5 07:38:46 Ricks-MacBook-Pro.local ReportCrash[2909]: Saved crash report for mdworker32[2910] version 707.3 to /Users/ricksmith/Library/Logs/DiagnosticReports/mdworker32_2013-01-05-073846-1_ Ricks-MacBook-Pro.crash

Jan  5 07:38:46 Ricks-MacBook-Pro.local ReportCrash[2909]: Removing excessive log: file://localhost/Users/ricksmith/Library/Logs/DiagnosticReports/mdworker32_2013 -01-05-073730_Ricks-MacBook-Pro.crash

Jan  5 07:38:52 Ricks-MacBook-Pro com.apple.launchd.peruser.501[152] (com.apple.mdworker.32bit.01000000-0000-0000-0000-000000000000[2911]): Job appears to have crashed: Segmentation fault: 11

 

What's the next step?

MacBook Pro (13-inch, Mid 2012), OS X Mountain Lion (10.8.2)
  • The hatter Level 9 Level 9 (58,545 points)

    That is a great FAQ and the user has done a great deal and over the years. But it doesn't mention testing memory (AHT does not do a good enough job). Rember or Memtest or even swapping out DIMMs.

     

    Spotlight issues I assume you fixed or resolved and deleted and rebuilt.

     

    CLONE your system both for testing and backup and to have an off line 2nd backup set and then start over with a clean system and gradually introduce programa and all the rest.

     

    And keep everything disconnected while you troubleshoot.

     

    Resolving Kernal Panics

    http://www.thexlab.com/faqs/kernelpanics.html

    http://reviews.cnet.com/8301-13727_7-10344626-263.html

    http://macs.about.com/od/usingyourmac/qt/Troubleshooting-Os-X-Kernel-Panics.htm

    http://support.apple.com/kb/TS3742

     

    You have a notebook, you posted in a forum for workstations, you might want to check that and also look in Mac OS community.

     

    MacBook Pro
    https://discussions.apple.com/community/notebooks/macbook_pro

    Mac Pro, Windows 8 Preview x64 3.2GHz
  • japamac Level 7 Level 7 (24,390 points)

    Add all hard drives to System Preferences/Spotlight/Options/Privacy.

    This will stop mdworker from activating to index the drives for Spotlight services.

    It should also stop the bog down and logging.

     

    This isn't, however, a fix, simply a workaround or test.

    Search functions will also be incomplete or disabled due to lack of drive indexing when a drive is placed in "Privacy".

     

    *

    FYI, mdworker will run virtually non-stop after a new OS install, a large backup or connection of a new, data filled drive. This is necessary to build indexes to allow searches of your hard drives, but consumes all CPU resources that mdworker can grab.

     

    Until the indexing is complete, the process will continue to sap resources.

     

    More:

    http://www.thexlab.com/faqs/stopspotlightindex.html

    *

     

    The EXC_BAD_ACCESS (SIGSEGV) could be RAM or other memory type (drive cache) related, as alluded to by The hatter.

    This is further supported by the log entry "Segmentation fault: 11" which refers to a memory error regarding access of an unassigned memory block.

     

    Sometimes this error is a bad programming issue, but may also be hardware related; memory, drive cache, drive block or sector, CPU, etc.

     

    Testing the RAM with one of the mentioned softwares would be prudent in my estimation.

    Testing with Memtest X in Single User mode will likely provide the most thorough test, as it allows testing of all memory with none left in reserve as when testing in the OS does.

  • japamac Level 7 Level 7 (24,390 points)

    If the MacBook Pro is still in warranty, use it.

    Call and get an appointment.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.