Extremely high load on mds/mdworker
Peter Eckel
since I upgraded to Mac OS X 10.6, I am noticing very high load
(30-60%) on the mds and mdworker processes. It is mainly noticable on
my MacBooks (Air/Pro) because of the fan running continually and the
'Books getting unusually hot.
At first I was not sure what was the cause of the problem, but all
symptoms point at Mailsmith:
- With version 2.2.1, the mds and mdworker32 process were running on
high load.
- After the upgrade to Mailsmith 2.2.2 (301), the high load shifted
from mdworker32 to mdworker. That coincides with the item in the
release notes that says "Change to build the Spotlight importer for
x86_64".
- I deleted the File Mailsmith.app/Contents/Library/Spotlight/
MailsmithImporter.mdimporter, and after a restart of the mds process
the CPU load is down, the 'Books run cool and everything is fine
again.
So the question is, is this a general problem with Mailsmith's
mdimporter's code, does it have to do something with my database, or
does someone have a better idea? I can live without Spotlight indexing
my mails for the time being, but if anyone should have a similar
problem it could be of general interest.
Regards,
Peter.
Steve Hodgson
thing here. Fans running flat out for no good reason and mds and
mdworker figuring high in the list of suspects.
I've reset the Spotlight index today and things seem better today.
Still more apparent use of fans than I would like.
Regards,
Steve
On 13 Sep 2009, at 17:50, Peter Eckel <pe-google...@hindenburgring.com
Peter Eckel
> I've reset the Spotlight index today and things seem better today.
> Still more apparent use of fans than I would like.
reset the indices, even disabled, deleted and re-enabled them and
sometimes there was some improvement for a while. But never for more
than a few hours. Completely disabling Spotlight indexing on the
computers main disk was effective, though too expensive in terms of
loss of functionality.
Regards,
Peter.
Doug White
(Peter Eckel) wrote:
>Hi,
>
>since I upgraded to Mac OS X 10.6, I am noticing very high load
>(30-60%) on the mds and mdworker processes. It is mainly noticable on
>my MacBooks (Air/Pro) because of the fan running continually and the
>'Books getting unusually hot.
...
>
>So the question is, is this a general problem with Mailsmith's
>mdimporter's code, does it have to do something with my database, or
>does someone have a better idea? I can live without Spotlight indexing
>my mails for the time being, but if anyone should have a similar
>problem it could be of general interest.
>
>Regards,
>
>Peter.
I was seeing a loss of battery life on my new Mac Book Pro after
upgrading to 10.6. Reports of high CPU use and low battery life
on other forums led me to look at mds and mdsworker. I disabled
them and thing are back to normal battery wise. The problem
seems pretty widespread, so it may be more than a Mailsmith
problem, more likely a spotlight bug that may interact badly
with a lot of different apps.
For now, Im living without spotlight.
Doug
Peter Eckel
> I was seeing a loss of battery life on my new Mac Book Pro after
> upgrading to 10.6. Reports of high CPU use and low battery life
> on other forums led me to look at mds and mdsworker. I disabled
> them and thing are back to normal battery wise. The problem
> seems pretty widespread, so it may be more than a Mailsmith
> problem, more likely a spotlight bug that may interact badly
> with a lot of different apps.
>
> For now, Im living without spotlight.
Spotlight issues, or even Spotlight itself having an issue in 10.6.
But, since I disabled Spotlight for Mailsmith and Mailsmith alone by
removing its importer and the problem disappeared immediately, the
Mailsmith importer seems to have been the only Software showing the
problem here, and on the other hand Mailsmith is definitely bit by the
bug. So if you remove the indicated file test-wise and mds/mdsworker
are back to normal after re-enabling Spotlight, we might know a little
bit more.
I would not really like to live without Spotlight, since I use it
fairly regularly, though not for mail.
Regards,
Peter.
Steve Hodgson
>- I deleted the File Mailsmith.app/Contents/Library/Spotlight/
>MailsmithImporter.mdimporter, and after a restart of the mds process
>the CPU load is down, the 'Books run cool and everything is fine
>again.
I came back home a couple of days ago to find the fans thrashing
away and the base of the MBP toasty warm. So after previously
resetting the Spotlight indexing, I decided to repeat your
experiment and things seemed to have calmed down here too.
Cheers,
Steve Hodgson
Jan Erik Moström
>>- I deleted the File Mailsmith.app/Contents/Library/Spotlight/
>>MailsmithImporter.mdimporter, and after a restart of the mds process
>>the CPU load is down, the 'Books run cool and everything is fine
>>again.
>
>I came back home a couple of days ago to find the fans
>thrashing away and the base of the MBP toasty warm. So after
>previously resetting the Spotlight indexing, I decided to
>repeat your experiment and things seemed to have calmed down
>here too.
I've had this symptom also but I don't think that Mailsmith has
been involved ... I think, I better check.
--
Jan Erik Moström, http://mostrom.eu
Ann Neumüller
I had the same thing: very high loads on mdworker (40-60% CPU
usage almost continuously). I deleted mdimporter a couple of
days ago and all is fine since then.
Ann
Jan Erik Moström
>I've had this symptom also but I don't think that Mailsmith has been
>involved ... I think, I better check.
I was wrong, it does seem to be Mailsmith related. Here is what
Activity Monitor reports before doing any changes at all: <http://emberapp.com/jemostrom/images/efter-omstart/sizes/m.png>
(the activity is caused by the mds and mdsworker32 processes)
If I remove the Mailsmith mdi importer plugin and restart then
it looks like this
<http://emberapp.com/jemostrom/images/efter-ta-bort-och-omstart/sizes/m.png>
So my guess is that the plugin has something to do with my
Spotlight problems
jem
Richard Fairbanks
this!), I am not having any such challenges; mds and mdsworker
(both running 64 bit) pop up into the 20’s every few seconds,
but spend most of the time at zero. Quitting Mailsmith doesn’t
seem to make much (if any) difference.
<2.33GHZ MBPC2D running Mac OS X 10.6.1 and Mailsmith 2.2.2 (301)>
Blessings,
Peter Eckel
excessive heat is back, mds/mdworker at high load.
Off you go, mdimporter ... :-(
Cheers,
Peter.
Steve Kalkwarf
> Just for the record: Upgraded to 2.2.2 (304) today, fans are on,
> excessive heat is back, mds/mdworker at high load.
We don't have any control over the process. For every message that
isn't in the Spotlight index, the OS loads our plugin, and says "Here,
index this file".
How much mail do you have?
What is the mds process doing when the load is high?
Peter Eckel
> How much mail do you have?
it mailing lists). But mds load wasn't an issue at all with 10.5, it
started to misbehave excatly when I upgraded to 10.6.
> What is the mds process doing when the load is high?
Cheers,
Peter.
Steve Kalkwarf
> About 60k, but low traffic (about 200-300 mails on a busy day, most of
> it mailing lists). But mds load wasn't an issue at all with 10.5, it
> started to misbehave excatly when I upgraded to 10.6.
I can't refrain from pointing out the obvious: If the symptom started
when you updated the OS, then maybe the OS is to blame?
>> What is the mds process doing when the load is high?
>
> How can I debug that?
I'd start by opening Console.app, and filtering the All Messages node
down to items containing "mdw". See if any errors or other diagnostics
are being logged.
Then, find the pid of the process that's working too hard, and:
sample <pid> 10 10
to see what code is running, and then
sudo fs_usage -w <pid>
to see what file(s) the process is looking at.
There are some forms of malformed message which cause the importer to
crash. Under 10.4 and 10.5, the message/file would be marked as a
crasher, and Spotlight would exclude it from the list of files to
index. It sounds like maybe that isn't happening under 10.6?
Steve
Jan Erik Moström
>We don't have any control over the process. For every message
>that isn't in the Spotlight index, the OS loads our plugin,
>and says "Here, index this file".
>
>How much mail do you have?
>
>What is the mds process doing when the load is high?
I think there is something else that is happening here. If I
re-index the whole disk Spotlight uses very little resources
until it's done - then it starts using a lot of CPU. The only
way I know to stop this is either to disable spotlight or remove
the Mailsmith Spotlight plugin.
Jason Davies
>
>I think there is something else that is happening here. If I re-index
>the whole disk Spotlight uses very little resources until it's done -
>then it starts using a lot of CPU. The only way I know to stop this is
>either to disable spotlight or remove the Mailsmith Spotlight plugin.
I seem to have a dance going on here having gone to 10.6.1. mds
and mdworker show something like the following CPU in Activity
Monitor on my dual core 2.4 gig aluminium
unibody-without-fire-I-should-have-waited, at roughly 5 second intervals:
mds 0.0 49.6 11 1.8 0.0 0.1 19.3 48.6
mdworker 0.0 39.0 16.0 2.4 0.1 0.0 17.9 38.8
in other words, leaping into action then vanishing, then
leaping. When they're both quiet, there is something like 30-60%
CPU idle so it doesn't seem to be something else snatching CPU.
Doubt that helps *specifically* but happy to send samples along
if this is worth investigating.
Robert W. Franson
>
>I think there is something else that is happening here. If I
>re-index the whole disk Spotlight uses very little resources
>until it's done - then it starts using a lot of CPU. The only
>way I know to stop this is either to disable spotlight or
>remove the Mailsmith Spotlight plugin.
>
>jem
By disabling Spotlight, do you mean turning off the app
altogether? Or just listing "Mailsmith User Data" as a folder
not to search under its Privacy options?
Robert W. Franson
Peter Eckel
> I can't refrain from pointing out the obvious: If the symptom started
> when you updated the OS, then maybe the OS is to blame?
does no longer work with the same program and 10.6, so the OS takes
part of the blame. But since Mailsmith is the only program having this
kind of problem while none of my other software products show the same
behaviour, there is at least a possibility that the reason is a bug in
Mailsmith that just didn't show up in older Mac OS releases.
> I'd start by opening Console.app, and filtering the All Messages node
> down to items containing "mdw". See if any errors or other diagnostics
> are being logged.
the problem. mds and mdworker do not seem to crash or otherwise log
problems when the high load occurs.
> sample <pid> 10 10
>
> to see what code is running, and then
>
> sudo fs_usage -w <pid>
>
> to see what file(s) the process is looking at.
install in order to get the mdimporter back - and noticed that there
is another new version, (306). You guys are too fast for me :-)
> There are some forms of malformed message which cause the importer to
> crash. Under 10.4 and 10.5, the message/file would be marked as a
> crasher, and Spotlight would exclude it from the list of files to
> index. It sounds like maybe that isn't happening under 10.6?
happening.
Cheers,
Peter.
Peter Eckel
On Sep 23, 11:03 pm, Jan Erik Moström <most...@gmail.com> wrote:
> I think there is something else that is happening here. If I
> re-index the whole disk Spotlight uses very little resources
> until it's done - then it starts using a lot of CPU. The only
> way I know to stop this is either to disable spotlight or remove
> the Mailsmith Spotlight plugin.
quietly for some time, then suddenly it is starting to go berserk. So
the problem seems to be reproducible.
One additional note: I am experiencing the exact same effect on my Mac
Book Air, which has only about 4k Mails in Mailsmith's Database. So I
think that an excessively large mail store can be ruled out as the
cause of the high load as well.
Cheers,
Peter.
Peter Eckel
would it be of any use for you if I sent you the output of the
fs_usage invocation?
I stopped collecting data about the mdworker after about 30 minutes,
by which time the file was about 80 MB large. Compressed about 3 MB.
The process runs on, though. From the output it looks like it is
indeed indexing Mailsmith's mail files, but one should expect that it
should finish in finite time:
[...]
02:19:22.373 lstat64 NMS.messageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd 0.000014 mdworker
02:19:22.373 getattrlist NMS.messageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd 0.000011 mdworker
02:19:22.373 getattrlist NMS.messageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd 0.000017 mdworker
02:19:22.373 open F=6 (R_____) NMS.messageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd 0.000016 mdworker
02:19:22.373 fstat64
F=6
0.000003 mdworker
02:19:22.373 fcntl F=6
<CHECK_OPENEVT>
0.000002 mdworker
02:19:22.373 flistxattr
F=6
0.000014 mdworker
02:19:22.373 flistxattr
F=6
0.000026 mdworker
02:19:22.373 stat NMS.messageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd 0.000010 mdworker
02:19:22.373 open F=7 (R_____) NMS.messageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd 0.000012 mdworker
02:19:22.373 read F=7
B=0x3ff
0.000007 mdworker
02:19:22.373 close
F=7
0.000006 mdworker
02:19:22.373 lstat [ 2] essageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd.lock 0.000022 mdworker
02:19:22.373 umask <---------
>
0.000001 mdworker
02:19:22.373 open F=7 (_WC__E) essageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd.lock 0.000081 mdworker
02:19:22.373 close
F=7
0.000009 mdworker
02:19:22.373 umask <----w--w-
>
0.000001 mdworker
02:19:22.373 chmod <rw-rw-rw-> essageData/
59910+MailsmithMessageData+C55A26E9-B2A0-4B12-A7B2-
F0DDC02E94E2.msgd.lock 0.000035 mdworker
[... and so on, and so forth]
The "sample" output follows:
Analysis of sampling mdworker (pid 22414) every 10 milliseconds
Call graph:
986 Thread_1208595 DispatchQueue_1: com.apple.main-thread
(serial)
986 0x10000120c
986 0x100008590
986 CFRunLoopRun
986 CFRunLoopRunSpecific
986 __CFRunLoopRun
986 mach_msg
986 mach_msg_trap
986 Thread_1208597 DispatchQueue_2: com.apple.libdispatch-
manager (serial)
986 start_wqthread
986 _pthread_wqthread
986 _dispatch_worker_thread2
986 _dispatch_queue_invoke
986 _dispatch_mgr_invoke
986 kevent
986 Thread_1208600
986 thread_start
986 _pthread_start
874 0x10000a390
874 0x10000a70b
874 mach_msg
874 mach_msg_trap
111 0x10000952e
63 0x100006410
63 close
46 0x1000060f5
46 GetMetadataForFile
46 GetMessageMetadata
41 mail_open
41 unix_open
40 unix_parse
39 unix_lock
39 dotlock_lock
30 crexcl
30 open
9 chmod
9 __chmod
1 unix_mbxline
1 unix_unlock
1 dotlock_unlock
1 unlink
1 __unlink
3 mail_fetch_structure
2 unix_text
2 unix_text_work
1 rfc822_parse_msg_full
1 cpystr
1 fs_get
1 mm_blocknotify
1 alarm
1 setitimer
1 CopyAddressHeaders(mail_stream*, char*)
1 fs_give
1 mm_blocknotify
1 alarm
1 setitimer
1 mail_close_full
1 mail_free_cache
1 mail_gc
1 mail_gc_msg
1 mail_free_body
1 mail_free_body_data
1 fs_give
1 mm_blocknotify
1 alarm
1 setitimer
1 0x1000052ec
1 0x100007214
1 -[NSCFDictionary setObject:forKey:]
1 CFDictionarySetValue
1 CFBasicHashSetValue
1 ___CFBasicHashFindBucket1
1 __CFBasicHashStandardCallback
1 0x1000052f3
1 0x10000a1cf
1 vm_deallocate
1 mach_msg
1 mach_msg_trap
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
mach_msg_trap 1861
kevent 986
close 63
open 30
__chmod 9
Cheers,
Pete.
Jan Erik Moström
>By disabling Spotlight, do you mean turning off the app
>altogether? Or just listing "Mailsmith User Data" as a folder
>not to search under its Privacy options?
Turning off indexing for the whole disk (I've never been a man
of subtle behavior :) but removing the Mailsmith plugin works best.
Jan Erik Moström
>I seem to have a dance going on here having gone to 10.6.1. mds
>and mdworker show something like the following CPU in Activity
>Monitor on my dual core 2.4 gig aluminium
>unibody-without-fire-I-should-have-waited, at roughly 5 second intervals:
This is what I used to see before removing the mailsmith plugin
<http://emberapp.com/jemostrom/images/spotlight/sizes/m.png>
efter removing the plugin
<http://emberapp.com/jemostrom/images/efter-ta-bort-och-omstart/sizes/m.png>
Peter Eckel
number of messages over and over. Definitely the indexing process
opens a lot more messages than I receive in the interval between two
mdworker invocations, it even seems to index messages even if there
have been no new ones at all.
An example: I just ran a fs_usage against an mdworker that has been
running for some time until it finished. A simple grep for open
operations on message files
grep 'open .*\.msgd ' mailsmith.fs_usage_4.txt | wc -l
shows 26604 hits, which, given the fact that each message file is
opened three times by Spotlight, indicates that at least 8868 message
files. That's quite a bit more than I have received in the last few
weeks, so either Spotlight forgets that the files are already indexed,
or something indicates to it that the file has changed and should be
indexed again. At the run before that one, at least 31362 files have
been opened (three times each), before that it was 43277. Since I did
not start fs_usage the same time the mdworker started (would have to
write some script for that, if necessary), I guess that Spotlight
always indexes *all* messages. Which would be a pretty good
explanation for the high load.
The big question ist: Why does Spotlight behave that way? And, more
important: How can I stop it doing this?
Cheers,
Peter.
Sven
what I did to get rid of the high load is to put the mailsmith mail
folder in your home directory to the private zone of spotlight.
Sven
Markus Lausecker
Sven
and what I did to get rid off it was to put the mailsmith mail folder
in my home directory to the private zone of spotlight.
Sven
HelgeGG
installing SL, now running 10.6.1. What may be interesting: after
updating to 2.2.2(304) the "high load behaviour" stopped but was again
re-introduced with 306-build! And this absolutely reproduceable: i
removed 306 and reinstalled 304, the mds load is gone...again
installing 306 and back again! So this may be some help to track it
down for the programmers...
Sven
mail folder in the users home directory to the private zone of
spotlight.
Sven
Sven Peters
what I did to get rid of the high load is to put the mailsmith
mail folder in your home directory to the private zone of spotlight.
Sven
Peter Eckel
another round ... the latest invocation of the mdworker obviously
opened 127743 message files (three times each ...). Which is much more
than I'd expect, since I don't even have 60000 Mails in my database.
Probably it indexed the message files more than once.
ardbeg:~ pete$ grep 'open .*\.msgd ' mailsmith.fs_usage_5.txt | wc -l
383228
Think I'll disable the mdimporter now for the weekend :-)
Steve, are you interested in the fs_usage output? If so, I can mail it
to you offline.
Cheers,
Peter.
Steve Kalkwarf
> another round ... the latest invocation of the mdworker obviously
> opened 127743 message files (three times each ...). Which is much more
> than I'd expect, since I don't even have 60000 Mails in my database.
> Probably it indexed the message files more than once.
That's just weird.
[...]
> Steve, are you interested in the fs_usage output? If so, I can mail it
> to you offline.
I don't think there's a lot to be learned beyond the snippet you
posted earlier, but go ahead and mail them to me.
Steve
Jan Erik Moström
<markus.l...@nepustil.net> wrote:
>How can the Mailsmith plugin be removed? Remove it from within
>the application package?
That is what I did
Steve Hodgson
>ardbeg:~ pete$ grep 'open .*\.msgd ' mailsmith.fs_usage_5.txt | wc -l
>383228
You've named your computer after an Islay single-malt whisky?
Don't you find all the subliminal messages throughout the day
too tempting?
I think I'll test the theory by renaming my machine Highland-Park.
Cheers (or Slàinte),
Steve Hodgson
Peter Eckel
> You've named your computer after an Islay single-malt whisky?
suffering from the same disease. I did not upgrade Lagavulin and
Glenkinchie yet, but probably the region is not that important.
> Don't you find all the subliminal messages throughout the day
> too tempting?
Not that that would be very effective at the moment.
> I think I'll test the theory by renaming my machine Highland-Park.
Slàinte,
Peter.
Peter Eckel
1. Locate the Mailsmith.app application file (which in fact is a
directory), by default it's in "/Applications"
2. Right-click (control-click, two-finger-tap) on the application,
select "Show Package Contents" and navigate to "Contents/Library/
Spotlight"
3. Delete the plugin.
You can also do it in Terminal using the command
rm -rf /Applications/Mailsmith.app/Contents/Library/Spotlight/
MailsmithImporter.mdimporter/
provided Mailsmith is located in /Applications.
Cheers,
Peter.
Peter Eckel
notes contains some fixes for the mdimporter.
No luck - I still have 30 messages (it seems) that Spotlight keeps
indexing again, again, and again (43920 times in less than three
minutes). So it's back to the broom closet for the mdimporter :-(
Cheers,
Peter.
Peter Eckel
No luck. The problem survived that treatment as well. Again, I'll
remove the importer and re-enter the idle loop :-)
Cheers,
Peter.
Jan Erik Moström
(Peter Eckel) wrote:
Same here
jem
--
Jan Erik Moström
http://mostrom.eu
Peter Eckel
The same procedure with (310), the same result, the same workaround.
Cheers,
Peter.
Jeroen Scheerder
>Another update (two in one day ... you guys are too fast for me :-)):
>
>The same procedure with (310), the same result, the same workaround.
After upgrading to 2.2.3 (310) I also noticed mdworker processes
consuming excessive amounts of CPU, and have disabled spotlight
for my Mailsmith User Data folder to restore sanity.
This did not happen, or I did not notice it, in any prior version.
Bill Rowe
>After upgrading to 2.2.3 (310) I also noticed mdworker processes
>consuming excessive amounts of CPU, and have disabled spotlight for
>my Mailsmith User Data folder to restore sanity.
>This did not happen, or I did not notice it, in any prior version.
FWIW, I have seen the issue of high cpu usage which *appears* to
be correlated with the Mailsmith mdimporter in previous versions
but not version 2.2.3 (with OQS 10.6.2) yet.
In the past when this has occurred I have "fixed" the problem by
dragging the mdimporter from the Mailsmith bundle and
re-booting. When I see the high cpu usage problem with an
mdworker process, this procedure consistently stops the mdworker
high cpu usage.
After "fixing" the problem, I have dragged the mdiporter back to
its original location. And this does not seem to cause the high
cpu usage to start backup. Even after re-booting with the
mdimporter back in its original position, the high cpu usage
problem does not seem to come back.
Note, the problem has returned after several days to weeks of
usage. But so far, I've been unable to find a set of conditions
that reliably causes the problem to occur on my system.
Peter Eckel
bit.
Now the cpu load is no longer permanent, but intermittent. I see a
five second interval of high load, followed by five seconds of quiet
CPU, and then high load again. Using fs_usage, I could confirm that it
is indeed the mdworker process running in those high load intervals on
Mailsmith messages (always the same ones, which is the same behaviour
as in the last versions). The CPU Graph looks like this: <http://
www.hindenburgring.com/CPU.pdf>
The machine does not run so hot anymore now, but the problem of the
mdimporter re-indexing the same mails over and over again is not gone,
I just hid under the bed.
Cheers,
Peter.
phil giltner
I too have mds working intermittently, running about 25% of CPU load.
This is frustrating, because I am one of those who depends upon
spotlight, and who keeps everything in his email. I have decommssioned
the MailsmithImporter.mdimporter by compressing it.
Steve Hodgson
I have ben having a couple of days of noticing my MacBook Pro running
VERY hot, then remembered about this issue (very unfortunately I've
had to move over to Apple Mail) and deleted the
MailsmithImporter.mdimporter file again.
Everything seems to be working fine again. As I don't use Spotlight
much this is no great hardship for me though, I can understand it
would be frustrating otherwise.
Regards (and happy new year),
Steve Hodgson
Peter Eckel
I installed 2.2.5 (314) yesterday, and the Spotlight problem is gone!
The machine is low on CPU when not used - neither constant nor
intermittent thrashing of the mdworker anymore.
Thanks Bare...um..Stickshift! As usual, you guys did a great job!
Cheers,
Peter.
Peter Eckel
too early.
I let my MB Air sit unattended for a few days, and when I returned to
it recently, it was running hot again, mdworker indexing Mailsmith
mails and obviously failing at it - same old story. Beats me why it
took so long to fall back into the old behaviour, but it seems that
the bug is still alive and kicking.
So it's delete-the-spotlight-importer-time again.
Cheers,
Peter.
Steve Kalkwarf
> I let my MB Air sit unattended for a few days, and when I returned to
> it recently, it was running hot again, mdworker indexing Mailsmith
> mails and obviously failing at it - same old story. Beats me why it
> took so long to fall back into the old behaviour, but it seems that
> the bug is still alive and kicking.
The messages you sent me a couple months ago no longer crash the importer, so that specific bug is fixed.
You must have another flavor of malformed message.
Steve
Peter Eckel
> The messages you sent me a couple months ago no longer crash the importer, so that specific bug is fixed.
OK, that's good to know.
> You must have another flavor of malformed message.
Obviously, the (people|mailing lists) that send mail to me are *very*
inventive ... "As soon as you design some idiot-proof software,
someone else designs a bigger idiot".
I'll investigate as soon as I can, and send you the new
idiot^H^H^H^H^Hmails, if that's that fine with you.
Cheers,
Peter.
Peter Eckel
I sent you some examples from the current 'mdworker crasher list'
offline.
Cheers,
Peter.
Ann Neumüller
I'm still having the same problem: high mdworker loads. Running
2.3 (407) now.
How exactly can I find out which messages are causing the problem?
Thanks,
Ann
On 2/02/10 at 00:37, pe-google...@hindenburgring.com