"mdworker quit unexpectedly while using the pixelmator plug-in"

Is something not working like it should? Let us know.
User avatar

2019-09-30 11:45:40

I occasionally get the following error message: "mdworker quit unexpectedly while using the pixelmator plug-in." The error doesn't seem to be connected with using the app. Instead it appears at random. Any known way to solve this?
User avatar

2019-10-03 15:21:21

Hi Christopher, this isn't a known issue as far as I'm aware — could you email us about it at support@pixelmator.com? Thanks in advance!
User avatar

2022-10-14 00:05:41

this isn't a known issue
:joy:

I have been experiencing this one daily, in a loop, for over a year now. I finally got fed up and googled. Can I email you too? Never mind, here is the crash log :stuck_out_tongue_winking_eye:
`Process:               mdworker [79094]
Path:                  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdworker
Identifier:            mdworker
Version:               1191.8
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           mdworker [79094]
User ID:               501

PlugIn Path:             /Applications/Pixelmator.app/Contents/Library/Spotlight/Pixelmator.mdimporter/Contents/MacOS/Pixelmator
PlugIn Identifier:       com.pixelmatorteam.pixelmator.SpotlightImporter
PlugIn Version:          ??? (201201.1932)

Date/Time:             2022-10-14 08:48:58.639 +0900
OS Version:            Mac OS X 10.13.6 (17G14042)
Report Version:        12
Anonymous UUID:        D21CB37F-EE1E-E105-2FFB-0BD9C43A6F8A

Sleep/Wake UUID:       EAF888ED-25A7-4928-8D58-AD9FDFF5568E

Time Awake Since Boot: 730000 seconds
Time Since Wake:       6500 seconds

System Integrity Protection: enabled

Crashed Thread:        4

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_MEMORY_ERROR at 0x0000000109d2e000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [0]

VM Regions Near 0x109d2e000:
    shared memory          0000000109cae000-0000000109d2e000 [  512K] r--/r-- SM=SHM  
--> mapped file            0000000109d2e000-0000000109dae000 [  512K] r--/rwx SM=COW  Object_id=7806cedb
    __TEXT                 000000010ce22000-000000010ce6d000 [  300K] r-x/rwx SM=COW  /usr/lib/dyld

Application Specific Information:
import fstype:dfsfuse_DFS fsflag:101A flags:40000007E diag:0 isXCode:0 uti:com.pixelmator.pxm plugin:/Pixelmator.app/Contents/Library/Spotlight/Pixelmator.mdimporter - find suspect file using: sudo mdutil -t 891

Application Specific Signatures:
import uti:com.pixelmator.pxm plugin:/Pixelmator.app/Contents/Library/Spotlight/Pixelmator.mdimporter uuid:C2A4E2CA-CFB4-42D8-B2F7-2BA130ECE292 201201.1932
Also a screenshot:
Image

Look all I really want to know is how to to disable your part of your app that is causing the crash loop.

I cannot "update my OS", 10.13 is as far as this computer will go; please also refrain from other non-help / lame suggestions like "reboot your computer" (tried it), "close and reopen Pixelmator" (funny thing is Pixelmator is not even running, but thanks), or "that version of Pixelmator/macOS/blah is no longer supported" (meh). That last bit of advice is the worst. I run Pixelmator on other, newer Macs where this doesn't happen. This is one Mac, at work, where I spend most of my time and suffer through this ridiculous crash daily. My request is very simple: tell me where to dig into your app and what I have to delete or what terminal command I can use to disable, turn off, or destroy whatever it is in Pixelmator that causes mdworker to crash.

Thank you for your time.