Abnormal HDD activity after launch MAX (maxdb-journal file) (SOLVED)


    Apr 04 2021 | 11:56 pm
    Hi guys
    Today observed strange behavior with 8.1.10, by some reason after launch MAX there is start abnormal HDD activity (up to 100%) and this is continues endlessly, until i exit program resp.
    Then i started to catch reason, thru Microsoft Procmon i found that program endlessly refresh\recreate one file in folder: C:\Users\*****\AppData\Roaming\Cycling '74\Max 8\Database\
    Filename: "d--program files-cycling '74-max 8-max.x64.maxdb-journal"
    Never seen such problem before, though can't say that often used Max in last times, but anyway. Ofcourse, before, hdd activity after the start of the program was naturally always present in one way or another (especially at the first start during one session of loading Windows), but usually ended quickly. Now there is clearly some problem.
    What could be the reason ?
    I almost did not change the settings (at least everything related to the location of the files - everything is by default).
    Win10 (1909) 64bit here , Max launched with admin rights.

    • Apr 05 2021 | 9:10 am
      Why creating or updating database is hanging, is difficult to say, maybe you have some HD problems... I would delete the whole database folder and start Max. If that does not help, and cycling support can't offer any help, this is a possible fix to at least allow Max to run : backup and delete or remove file sqlite.mxe64 from Max installation /resources/extensions/max/ That would disable max database functions, would throw few errors at Max start, and one would need to force quit Max.exe instead of simply quit.
      TASKKILL /F /IM Max.exe /T paste line above into notepad, save as KillMax.cmd if you run Max with admin rights, then run script so as well
    • Apr 05 2021 | 4:26 pm
      @ SOURCE AUDIO ok ty for info, will try. About HDD problems - well no. I regularly monitor to hdd thru CrystalDiskInfo. And besides, naturally then i would had problems not with Max only.
    • Apr 08 2021 | 4:58 pm
      UPDATE: sorry for false call. After some time, the activity suddenly dropped to zero, apparently it took time for something to be combed there. And subsequent launches of Max no longer cause such activity, it stops quickly enough.