If you’re using Mojave then Apple has “conveniently” relocated the place where it asks sandboxed apps to store all their temp/cache/pref files. The old “Containers” folder is now called “Group Containers” and recently released apps should have their company “group ID” prefixing their already cryptic backwards company ID.
The result is that you can now find all of the RW detritus in:
You may also have similar containers for previous variants. My group containers folder looks like this:
RW v8.1 and later uses the first one. I still have to use RW 8.0 and RW 7.x a lot so even though I’m working on my brand spanking new hackintosh machine I have all three.
I run a very tight ship and regularly just delete these directories completely. If I can’t reproduce someone’s error, sometimes it’s little things, like the latency for creating a new unique tmp folder when there are 30,000 tmp folders in here for some unknown reason.
In most cases RW and Stacks clean up after themselves and there’s not much even worth deleting in here, but if RW does not shut down cleanly, then all of the cleanup might not happen. This is rarely an issue.
In my case automated testing may fail – producing a crash – and stranding some cache and tmp files. And on some productive days I can run automated tests all day long over and over – so thousands of these things build up all of a sudden and before you know it there’s 150GB of cache data sitting in there. 😲
Even in that really contrived situation the effects of that built up crud is difficult for me to detect, even with tools that are measuring performance. So… this is really the last resort of trying to look for odd RW behavior.
OK, what to do:
Before you begin:
Please know that this will wipe out pretty much all the RW data. This might include RW license info (RW stores its license info in different places depending on how you bought it – so your milage may vary here) – but have you license info on hand just in case.
Yeah, I know. Pain in the butt. But the thing is macOS keeps preferences (technically called “User Defaults”) synchronized to an in-memory database. If you yank the rug out from that database while it’s synchronizing weird shit can happen. So, really do a reboot. This time it’s not just the IT guy doing it for no reason. There’s a reason and it’s a good one.
DONT launch RW.
For the same reason. We want to delete these files before the in-memory prefs db starts to synchronize with the prefs files on-disk.
Drag the folder
~/Library/Group Containers/P97H7FTHWN.com.realmacsoftware.rapidweaver to the Desktop
OK, I’m not sure if this reboot is 100% necessary. But I read it in someone else’s similar instructions, so I’m parroting that here. 🦜
Start up RW.
You may have to re-register RW. You will definitely have to re-register Stacks. You’ll have to tell RW where your add-ons directory lives again too.
Like I said, I would not expect this to have any measurable performance gains – but it is the one way to absolutely, positively start completely fresh. Good luck.