DOM memory system
|DOM 1.3||This revision of this article is current for COLLADA DOM version 1.3.|
Summary: Internal notes on the COLLADA DOM memory system.
daeMemory system is supposed to be a class that manages the COLLADA DOM's memory from different heap pools:
- It overwrites
- All dae classes overwrite
deleteto use the
This has never been fully implemented. It actually makes it harder to profile the DOM because many memory profilers replace
malloc/free with their own functions but, since the DOM does that also, they don’t work.
|COLLADA DOM - Version 2.4 Historical Reference|
|List of main articles under the DOM portal.|
| User Guide chapters: • Intro • Architecture • Setting up • Working with documents • Creating docs • Importing docs • Representing elements • Working with elements • Resolving URIs • Resolving SIDs • Using custom COLLADA data • Integration templates • Error handling|
Systems: • URI resolver • Meta • Load/save flow • Runtime database • Memory • StringRef • Code generator