# Memory Manager Development

DevFeed: [Memory Manager Development](<https://devfeed.tech/articles/memory-manager-development-32860.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/memory-manager-development/>)

Published: 2014-09-09T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [ReactOS](<https://devfeed.tech/topics/reactos.md>), [Development](<https://devfeed.tech/topics/development.md>), [legacy](<https://devfeed.tech/topics/legacy.md>)

Tags: [development](<https://devfeed.tech/tags/development.md>), [free](<https://devfeed.tech/tags/free.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [opensource](<https://devfeed.tech/tags/opensource.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

ReactOS is rewriting parts of its legacy memory manager through the ARM3 project. The rewrite has partially replaced the old manager, while MEMORY_AREA remains under its responsibility for tracking memory address ranges needed for paging.

## Source excerpt

The legacy memory manager in ReactOS has many idiosyncrasies and architectural quirks, issues that have dogged the project for many years now. The ARM team began a rewrite, colorfully named Another Rewrite of the Memory Management Module (ARM3), that partially supplanted the old memory manager but a big chunk of responsibility still lie with it, namely in the form of MEMORY_AREA. Simply put, MEMORY_AREA was the means by which memory address ranges were tracked, tracking which is necessary for things like handling paging.