Repository navigation
[Bug]: massCode.db-shm is in use and Onedrive is pending sync #635
Description
Describe the bug
In the new release version （V4）, onedrive always reports that massCode.db-shm is in use and thus is pending sync, while in previous version (v3) does not trigger this issue.
To reproduce
- Put the database file in onedrive
- use masscode 4 and open repo from onedrive folder.
App Version and Architecture
4.2.2
System info
System:
OS: Windows 11 10.0.26200
CPU: (16) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
Memory: 40.24 GB / 79.80 GBValidations
- Follow our Code of Conduct
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion.
Activity
antonreshetov commentedon Nov 11, 2025
Starting from v4, massCode uses SQLite3 as the database engine, whereas v3 stored data in plain JSON files.
SQLite uses auxiliary files like massCode.db-shm and massCode.db-wal for write-ahead logging and synchronization.
These files remain open while the application is running, which can cause OneDrive (and other sync tools) to show them as “in use” or “pending sync.”
This behavior is normal for SQLite and doesn’t affect your data integrity.
If you need to sync your workspace via OneDrive, it’s best to let it sync only after closing massCode.