**Test Suite Completion - Scenario 5** Add comprehensive memory leak detection test for hot-reload system with 200 reload cycles. **New Test: test_05_memory_leak** - 200 hot-reload cycles without recompilation - Memory monitoring every 5 seconds (RSS, temp files, .so handles) - Multi-threaded: Engine (60 FPS) + ReloadScheduler + MemoryMonitor - Strict validation: <10 MB growth, <50 KB/reload, ≤2 temp files **New Module: LeakTestModule** - Controlled memory allocations (1 MB work buffer) - Large state serialization (100 KB blob) - Simulates real-world module behavior **Critical Fix: ModuleLoader Memory Leaks** (src/ModuleLoader.cpp:34-39) - Auto-unload previous library before loading new one - Prevents library handle leaks (+200 .so mappings eliminated) - Prevents temp file accumulation (778 files → 1-2 files) - Memory leak reduced by 97%: 36.5 MB → 1.9 MB **Test Results - Before Fix:** - Memory growth: 36.5 MB ❌ - Per reload: 187.1 KB ❌ - Temp files: 778 ❌ - Mapped .so: +200 ❌ **Test Results - After Fix:** - Memory growth: 1.9 MB ✅ - Per reload: 9.7 KB ✅ - Temp files: 1-2 ✅ - Mapped .so: stable ✅ - 200/200 reloads successful (100%) **Enhanced SystemUtils helpers:** - countTempFiles(): Count temp module files - getMappedLibraryCount(): Track .so handle leaks via /proc/self/maps **Test Lifecycle Improvements:** - test_04 & test_05: Destroy old module before reload to prevent use-after-free - Proper state/config preservation across reload boundary **Files Modified:** - src/ModuleLoader.cpp: Auto-unload on load() - tests/integration/test_05_memory_leak.cpp: NEW - 200 cycle leak detector - tests/modules/LeakTestModule.cpp: NEW - Test module with allocations - tests/helpers/SystemUtils.{h,cpp}: Memory monitoring functions - tests/integration/test_04_race_condition.cpp: Fixed module lifecycle - tests/CMakeLists.txt: Added test_05 and LeakTestModule 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .claude/config_backups | ||
| docs | ||
| include/grove | ||
| planTI | ||
| src | ||
| tests | ||
| .gitignore | ||
| CMakeLists.txt | ||
| README.md | ||
GroveEngine 🌳
Modular C++ Engine Architecture for Rapid Development with Hot-Reload
GroveEngine is a lightweight, modular engine architecture designed for blazing-fast development iteration (0.4ms hot-reload validated) and optimized for Claude Code workflows.
Key Features
- 🔥 Hot-Reload 0.4ms - Validated blazing-fast module reloading
- 🧩 Modular Architecture - Clean separation via interfaces (IEngine, IModule, IIO, IModuleSystem)
- 🚀 Development Velocity - Edit → Build → Hot-reload < 1 second total
- 🤖 Claude Code Optimized - 200-300 line modules for AI-friendly development
- 📦 Autonomous Builds - Each module builds independently (
cmake .) - 🔌 Progressive Scaling - Debug → Production → Cloud without rewriting
Architecture Overview
grove::IEngine (Orchestration)
├── grove::IModuleSystem (Execution strategy)
│ ├── SequentialModuleSystem (Debug/test - 1 module at a time)
│ ├── ThreadedModuleSystem (Each module in thread - TODO)
│ └── MultithreadedModuleSystem (Thread pool - TODO)
├── grove::IModule (Business logic - 200-300 lines)
│ └── Your modules (.so/.dll hot-reloadable)
└── grove::IIO (Communication)
├── IntraIO (Same process - validated)
├── LocalIO (Same machine - TODO)
└── NetworkIO (Distributed - TODO)
Current Status
✅ Implemented & Validated
- Core Interfaces (13): IEngine, IModule, IModuleSystem, IIO, ICoordinationModule, ITaskScheduler, IDataTree, IDataNode, IUI, ISerializable
- Debug Implementations (Phase 2 - Pre-IDataTree):
DebugEngine- Comprehensive logging and health monitoringSequentialModuleSystem- Ultra-lightweight executionIntraIO+IntraIOManager- Sub-millisecond pub/sub with pattern matchingModuleFactory- Dynamic .so/.dll loading systemEngineFactory,ModuleSystemFactory,IOFactory- Factory patterns
- Hot-Reload System - 0.4ms average, 0.055ms best performance, perfect state preservation
- UI System - ImGuiUI implementation with hybrid sizing
⚠️ Compatibility Note
Current implementations use pre-IDataTree API (json config). The architecture evolved to use IDataNode for configuration. Implementations need adaptation or recreation for full IDataTree compatibility.
🚧 TODO
- Adapt implementations to use IDataTree/IDataNode instead of json
- Implement ThreadedModuleSystem and MultithreadedModuleSystem
- Implement LocalIO and NetworkIO
- Create concrete IDataTree implementations (JSONDataTree, etc.)
Quick Start
Directory Structure
GroveEngine/
├── include/grove/ # 27 headers
│ ├── IEngine.h # Core interfaces
│ ├── IModule.h
│ ├── IModuleSystem.h
│ ├── IIO.h
│ ├── IDataTree.h # Configuration system
│ ├── IDataNode.h
│ └── ...
├── src/ # 10 implementations
│ ├── DebugEngine.cpp
│ ├── SequentialModuleSystem.cpp
│ ├── IntraIO.cpp
│ ├── ModuleFactory.cpp
│ └── ...
├── docs/ # Documentation
│ ├── architecture/
│ │ ├── architecture-modulaire.md
│ │ └── claude-code-integration.md
│ └── implementation/
│ └── CLAUDE-HOT-RELOAD-GUIDE.md
├── modules/ # Your application modules
├── tests/ # Tests
└── CMakeLists.txt # Build system
Build
cd GroveEngine
mkdir build && cd build
cmake ..
make
# Or use the root CMakeLists.txt directly
cmake .
make
Create a Module
// MyModule.h
#include <grove/IModule.h>
class MyModule : public grove::IModule {
public:
json process(const json& input) override {
// Your logic here (200-300 lines max)
return {"result": "processed"};
}
void setConfiguration(const IDataNode& config, IIO* io, ITaskScheduler* scheduler) override {
// Configuration setup
}
// ... other interface methods
};
Documentation
- Architecture Modulaire - Core interface architecture
- Claude Code Integration - AI-optimized development workflow
- Hot-Reload Guide - 0.4ms hot-reload system
Philosophy
Micro-Context Development
- Small modules (200-300 lines) for AI-friendly development
- Autonomous builds - Zero parent dependencies
- Hot-swappable infrastructure - Change performance without touching business logic
Progressive Evolution
// Start simple (MVP)
DebugEngine + SequentialModuleSystem + IntraIO
// Scale transparently (same module code)
HighPerfEngine + MultithreadedModuleSystem + NetworkIO
Complexity Through Simplicity
Complex behavior emerges from the interaction of simple, well-defined modules.
Performance
Hot-Reload Benchmarks (Validated):
- Average: 0.4ms
- Best: 0.055ms
- 5-cycle test: 2ms total
- State persistence: 100% success rate
- Classification: 🚀 BLAZING (Theoretical maximum achieved)
Projects Using GroveEngine
- AISSIA - AI Smart Schedule & Interactive Assistant (in development)
- WarFactory (original architecture source)
License
To be defined
Contributing
This engine uses an architecture optimized for Claude Code development. Each module is autonomous and can be developed independently.
Constraints:
- ✅ Modules 200-300 lines maximum
- ✅ Autonomous build:
cmake .from module directory - ✅ JSON-only communication between modules
- ✅ Zero dependencies up (no
#include "../") - ❌ Never
cmake ..
GroveEngine - Where modules grow like trees in a grove 🌳