Skip navigation

mdworker32 takes up 97% of CPU all the time?

70660 Views 36 Replies Latest reply: Mar 21, 2013 11:09 AM by HornBlowR RSS
1 2 3 Previous Next
Viztang Level 1 Level 1 (0 points)
Currently Being Moderated
Sep 6, 2009 9:20 AM
Hi all,
I have been suffering from mdworker32 taking up to 97% of the CPU. This lead to a mechanical failure of HD days ago and apple replaced one for me. However, the phenomenon still exits.

Details: MBPro late 2008 unibody 2.4G 4G and 320 HD
After upgrade to SL, the system keeps running at a high fan status. Roughly around 4000, and one process, mdworker32 keeps taking 97% of the CPU (20% of total) power.
I removed all importers from /Library/Spotlight but this didn't help.

An inspection in console suggesting the mdworker32 keeps throw exit code 75? (Anyone know what this means?)


Thanks much,
Sean
Macbook Pro, Mac OS X (10.6), 2.4G/4G/320
  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Sep 6, 2009 5:12 PM (in response to Viztang)
    Viztang wrote:
    Hi all,
    I have been suffering from mdworker32 taking up to 97% of the CPU. This lead to a mechanical failure of HD days ago and apple replaced one for me. However, the phenomenon still exits.

    Details: MBPro late 2008 unibody 2.4G 4G and 320 HD
    After upgrade to SL, the system keeps running at a high fan status. Roughly around 4000, and one process, mdworker32 keeps taking 97% of the CPU (20% of total) power.
    I removed all importers from /Library/Spotlight but this didn't help.


    Not a good idea. It won't ever run right without them.

    Exclude your internal HD (and any externals) from Spotlight indexing via System Preferences > Spotlight > Privacy. That should stop it, but won't fix it.

    Post back with the results, and also what, if any, other disks/partitions are attached, whether you have any disk images/sparse bundles, and whether you're using File Vault.
    24" iMac 2.66 GHz Intel; 4gb; 640 gb, Mac OS X (10.6), AEBS
  • OverPowerFred Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 22, 2009 10:50 PM (in response to Viztang)
    Hi,

    I have been contacting Apple Support to solve this issue and it seems it is solved so far. The issue is linked to Spotlight and MSOffice 2008. Even after uninstalling MSOffice, the issue wasn't solved until the file +Microsoft Office.mdimporter+ has been manually removed from Macintosh>Library>Spotlight>+Microsoft Office.mdimporter+. Check if you also have something similar in Username>Library>Spotlight>. Once you have done that, you can index you HD with SL without having problems with mdworker32.
    Remember that if you reinstall MSOffice, you will probably need remove those files once more to prevent the problem to reappear.
    MacBook Pro 17'' 2.8GHz, Mac OS X (10.6.1)
  • paranous Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 8, 2009 8:44 AM (in response to OverPowerFred)
    Hi,

    I don't think this problem has been resolved. At least, I don't seem to have the MicrosoftOffice.mdimporter file on my computer and the mdworker32 process still hogs CPU and I don't know how to fix it. I have the most recent version of Mac OS (10.6.2).

    Are there any other suggestions?
    Macbook 5.1, Intel Core Duo 2, Mac OS X (10.6.2)
  • Martin Garmendia Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 18, 2009 1:35 AM (in response to paranous)
    This seems to be a mdimporters problem. To see which mdimporter is causing the problem go to +Activity Monitor+, double click mdworker32 and select +Open files and ports+ tab. You can see there which mdimporters are used, so you can go to their respective folders and rename or delete them.
    Macbook 4.1, Mac OS X (10.6.2)
  • panos_tsapralis Level 1 Level 1 (10 points)
    I have been having the same problem and the only way I found so far to deal with it was to exclude my entire internal hard disk drive from the SL indexing process by going to System Preferences -> Spotlight -> Privacy and adding that drive to the list. CPU load has gone back to normal ever since - however, I don't know what are the deeper implications of this configuration.
    MacBook Pro Aluminum Unibody 13.3", Intel Core 2 Duo - 2.53 GHz, 4 GB, 250 GB, Mac OS X (10.6.2), Parallels Desktop, VMWARE Fusion, SUN Virtual Box, iPhone 3G 16 GB
  • FrequentFlyer Level 1 Level 1 (5 points)
    Currently Being Moderated
    Dec 29, 2009 11:16 AM (in response to Viztang)
    I've had this problem on my Intel quad core PowerMac ever since I installed the update to Office 2008 a few days ago. Sometimes I wonder if Microsoft intentionally cripples their Apple software to make their platform seem more desirable.

    I'm going to remove Office 2008 and reinstall the original programs.
    PowerMac Dual 2.0 G5, Mac OS X (10.4.4), 4.5 GB RAM, Nvidia 6800 Ultra
  • panos_tsapralis Level 1 Level 1 (10 points)
    Currently Being Moderated
    Dec 29, 2009 11:54 AM (in response to FrequentFlyer)
    I am not completely sure that Microsoft Office 2008 or any of its update causes this behavior I wouldn't be surprised if it did, though...). A little bit of experiment wouldn't hurt, however - so, let us know what happens when you uninstall MS Office 2008 or its latest update. I am thinking of doing something similar: now, that I have upgraded to Snow Leopard, I am planning to switch to OPENOFFICE.ORG or NEOOFFICE and replace Microsoft Entourage 2008 with MAC OS X Mail.

    Panos.
    MacBook Pro Aluminum Unibody 13.3", Intel Core 2 Duo - 2.53 GHz, 4 GB, 250 GB, Mac OS X (10.6.2), Parallels Desktop, VMWARE Fusion, SUN Virtual Box, iPhone 3G 16 GB
  • FrequentFlyer Level 1 Level 1 (5 points)
    I removed Office 2008 and the problem persists.
    Mac Pro Dual 2.66 Intel Xeon, Mac OS X (10.6.2), 10 GB RAM
  • txrpls Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 5, 2010 5:54 AM (in response to FrequentFlyer)
    Booting in 64 bit mode seems to solve this problem.
    Mac Book Pro 17, Mac OS X (10.6.2)
  • panos_tsapralis Level 1 Level 1 (10 points)
    Currently Being Moderated
    Jan 5, 2010 7:54 AM (in response to txrpls)
    What does "booting in 64 bit mode" mean? How do I do it? When I bought my latest MBP (with Snow Leopard) I restored my old contents from an up-to-date Time Machine backup - can I use 64 bit mode now? What are the implications, if any?

    TIA,
    MacBook Pro Aluminum Unibody 13.3", Intel Core 2 Duo - 2.53 GHz, 4 GB, 250 GB, Mac OS X (10.6.2), Parallels Desktop, VMWARE Fusion, SUN Virtual Box, iPhone 3G 16 GB
  • Marek Stepanek Level 2 Level 2 (290 points)
    Hello all!

    I have had also a problem with this indexing, when I was connecting to an external HD. How can Apple conceive such a thing, indexing foreign Documents? I thought this is Google or Microsoft style!

    I never work with spotlight; and I don't like to be treated as child from my OS. So I only use in my Shell commands like: % locate find grep

    This is largely sufficient. To switch of the indexing of spotlight on SnowLeopard, make the following command in your shell:

    % sudo mdutil -a -i off (without the % off course! If you want to switch it on, you simply put a "on" to the end of this command. Obvious!)

    If you need information about this command:

    % man mdutil

    And to remove the index-files, go to your root-folder:

    % cd /

    and remove the following folder with:

    % sudo rm -rf .Spotlight*

    *Don't remember the exact name of this folder again ... But with the "*" at the end, this command is working too


    marek
    MBP 17, Mac OS X (10.6.2)
  • mishichan Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 10, 2010 12:58 AM (in response to Viztang)
    I've deleted stuffit and problem has gone.
    iMac, Mac OS X (10.6.2)
1 2 3 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (2)

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.