Quick Diagnosis
Run these commands to quickly identify issues:Common Issues
”File is locked” when opening
Symptoms
Symptoms
FileLocked: File is locked by another process- Operations hang indefinitely
- Cannot open file in Python/Node.js
Diagnosis
Diagnosis
Solution
Solution
- Wait for the other process to finish
- Kill the blocking process (if stuck):
- Open in read-only mode:
- Check for crashed processes - if a process crashed while holding a lock, restart your terminal/IDE
Search returns no results
Symptoms
Symptoms
mem.find()returns empty results- CLI search shows “0 results”
- Expected documents not appearing
Diagnosis
Diagnosis
Solution
Solution
-
Verify content exists:
-
Check search mode - try
lexfor exact matches,semfor semantic: -
Rebuild indices if they’re corrupted:
-
Check embeddings were enabled during ingestion:
“CapacityExceeded” error
Symptoms
Symptoms
CapacityExceeded: Memory file exceeded capacity limitput()operations fail- Cannot add new content
Diagnosis
Diagnosis
Solution
Solution
-
Upgrade your plan for more capacity:
-
Delete old content:
-
Vacuum to reclaim space:
-
Archive and create new file:
Slow query performance
Symptoms
Symptoms
- Queries taking >100ms
- Timeouts on large files
- High memory usage during search
Diagnosis
Diagnosis
Solution
Solution
-
Reduce
kvalue for fewer results: -
Use specific search mode:
-
Add scope filters:
-
Enable vector compression for smaller index:
-
Split into multiple files for very large datasets:
Import errors in Python
Symptoms
Symptoms
ImportError: cannot import name 'use' from 'memvid_sdk'ModuleNotFoundError: No module named 'memvid_sdk'ImportError: libmemvid.so not found
Diagnosis
Diagnosis
Solution
Solution
-
Install/reinstall the SDK:
-
Check Python version (requires 3.8+):
-
Use correct virtual environment:
-
On Apple Silicon, ensure you’re using native Python:
Native binding errors in Node.js
Symptoms
Symptoms
Error: Cannot find module '../index.node'Error: The module was compiled against a different Node.js version- Segmentation fault on import
Diagnosis
Diagnosis
Solution
Solution
-
Reinstall with rebuild:
-
Check Node.js version (requires 18+):
-
Install build tools if needed:
File corruption after crash
Symptoms
Symptoms
CorruptFile: Invalid header magic bytesVerificationFailed: Checksum mismatch- File won’t open after system crash
Diagnosis
Diagnosis
Solution
Solution
-
Run the doctor command:
-
Rebuild indices:
-
If recovery fails, restore from backup:
-
Prevent future corruption:
- Always call
mem.seal()before exiting - Use UPS/battery backup for critical systems
- Enable automatic backups
- Always call
Framework adapter not working
Symptoms
Symptoms
mem.toolsreturns empty or None- Framework-specific methods missing
- Type errors with framework objects
Diagnosis
Diagnosis
Solution
Solution
-
Install the framework dependency:
-
Use correct adapter name:
-
Check framework version compatibility: