Sidebar: the MM27 from Oct 10, 2026 was installed in portable mode and still overwrote the MM2024 settings as both tried to put themselves into the %appdata%/blah/MM5 folder
I have tried:
- creating a new DB
converting an MM4 DB
using an older working MM2024 DB
I am not sure if it has to do with the number of files or the number of folders it is scanning. I have another "working" folder with 254,257 files in it and has 27,733 folders and subfolders. There are no issues scanning it.
the problematic folder has 511,684 files and 262,860 subfolders (starts with first letter of file, so there are ~35-40 main folders, then subfolders). it will always fail around the letter "C" or "D", some ~40K folders in. I have tried smaller sets, but that kind of ruins the functionality and takes far longer to do. Even then, it is random... an hour ago, it consumed 18,802 folders and 33,546 files in "M" but when I tried the main folder "N" it failed twice. it has 9740 folders and 44,105 files ... far less than the "working" folder. sometimes the DB keeps the last import, sometimes it does not, even though the journal file is ingested on restart. i have to resort to using a backup to start from the last successful import
When I did this in batches before, it "sorta kinda" worked in that after 25 batches, i could then scan the entire folder but now that is not working.
The machine is a Windows 11, with 96GB of RAM i7-13700 running off of NVMEs. Database is local, files are on a local Win10 machine. MM2024 is v2024.2.2.3222, lifetime version. No other programs are hitting the system at the time.
The error is shown below:
https://imgur.com/a/j2T4CFf
EDIT: None of the three options in the crash dialog (restart, restart in safe mode, continue) work... MM exits ungracefully and does not restart.
Would it have made a difference if this was an actual 64 bit app? i find it hard to believe the 32bit app crashes so much when the even older version does not.
any help is appreciated.