From Newsgroup: comp.sys.acorn.apps

I keep getting memory errors in my Reporter window and finding my Task
Manager full of dynamic areas of exactly 208480K with names like mmap#1
or mmap#5 which persist even after quitting all likely culprit
applications - which software is filling up the computer's memory with
these, and is it a bug?
--
Harriet Bazley == Loyaulte me lie ==

It is better to wear out than to rust.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

In message <5d993ef15c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

I keep getting memory errors in my Reporter window and finding my Task Manager full of dynamic areas of exactly 208480K with names like mmap#1
or mmap#5 which persist even after quitting all likely culprit
applications - which software is filling up the computer's memory with
these, and is it a bug?

I believe mmap = memory map. per an online search
Iris seems to be one application that uses it. when you quit it, the mmap
is reduced or removed
I don't think it is a bug.

Maybe you need to let Martin Avison know about the error in reporter.
--
Chris Hughes
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

In article <11db74f15c.chris@mytardis>,
Chris Hughes <news13@noonehere.co.uk> wrote:

In message <5d993ef15c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

I keep getting memory errors in my Reporter window and finding my
Task Manager full of dynamic areas of exactly 208480K with names
like mmap#1 or mmap#5 which persist even after quitting all
likely culprit applications - which software is filling up the
computer's memory with these, and is it a bug?

I believe mmap = memory map. per an online search Iris seems to be
one application that uses it. when you quit it, the mmap is
reduced or removed I don't think it is a bug.

Maybe you need to let Martin Avison know about the error in
reporter.

I agree mmap#n areas are asociated with Iris, but I suspect Reporter
was just reporting errors in Iris that are causing the areas to
accumulate? Perhaps Harriet can clarify.
--
Martin Avison
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

On 1 Jul 2026 as I do recall,
Martin wrote:

In article <11db74f15c.chris@mytardis>,
Chris Hughes <news13@noonehere.co.uk> wrote:

In message <5d993ef15c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

I keep getting memory errors in my Reporter window and finding my
Task Manager full of dynamic areas of exactly 208480K with names
like mmap#1 or mmap#5 which persist even after quitting all
likely culprit applications - which software is filling up the
computer's memory with these, and is it a bug?

I believe mmap = memory map. per an online search Iris seems to be
one application that uses it. when you quit it, the mmap is
reduced or removed I don't think it is a bug.

Maybe you need to let Martin Avison know about the error in
reporter.

I agree mmap#n areas are asociated with Iris, but I suspect Reporter
was just reporting errors in Iris that are causing the areas to
accumulate? Perhaps Harriet can clarify.

Yes, the Reporter window is just displaying the error reports -
presumably because the application in question (I'm fairly sure it's
NetSurf giving the actual errors) is RISC OS native and is using
Reporter's SWIs in its debugging. :-)

To clarify: these are messages appearing (in black) in the Reporter
window and not Wimp errors being logged by Reporter, e.g.

dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_claim_pages:151 - Memory cannot be moved dynamicarea_claim_pages:151 - Memory cannot be moved
--
Harriet Bazley == Loyaulte me lie ==

Own nothing you do not know to be useful or believe to be beautiful.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

Bonjour,
In message <0a6d7cf15c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

On 1 Jul 2026 as I do recall,
Martin wrote:

In article <11db74f15c.chris@mytardis>,
Chris Hughes <news13@noonehere.co.uk> wrote:

In message <5d993ef15c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

I keep getting memory errors in my Reporter window and finding my
Task Manager full of dynamic areas of exactly 208480K with names
like mmap#1 or mmap#5 which persist even after quitting all
likely culprit applications - which software is filling up the
computer's memory with these, and is it a bug?

I believe mmap = memory map. per an online search Iris seems to be
one application that uses it. when you quit it, the mmap is
reduced or removed I don't think it is a bug.

Maybe you need to let Martin Avison know about the error in
reporter.

I agree mmap#n areas are asociated with Iris, but I suspect Reporter
was just reporting errors in Iris that are causing the areas to
accumulate? Perhaps Harriet can clarify.

Yes, the Reporter window is just displaying the error reports -
presumably because the application in question (I'm fairly sure it's
NetSurf giving the actual errors) is RISC OS native and is using
Reporter's SWIs in its debugging. :-)

To clarify: these are messages appearing (in black) in the Reporter
window and not Wimp errors being logged by Reporter, e.g.

dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_claim_pages:151 - Memory cannot be moved dynamicarea_claim_pages:151 - Memory cannot be moved

Do dynamicarea_map_pages correspond to dynamic area numbers?
It seems to me that all DA numbers are above 255.
Hariett, are you still using your ARMX6?
--
Jean-Michel
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

On 2 Jul 2026 as I do recall,
Jean-Michel wrote:

[snip]

dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_claim_pages:151 - Memory cannot be moved dynamicarea_claim_pages:151 - Memory cannot be moved

Do dynamicarea_map_pages correspond to dynamic area numbers?

Probably not - more likely these are error values of some sort?

It seems to me that all DA numbers are above 255.
Hariett, are you still using your ARMX6?

Yes, this is on an ARMX6.
--
Harriet Bazley == Loyaulte me lie ==

It is better to be deceived by a friend, than to suspect him.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

In message <f22693f25c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

On 2 Jul 2026 as I do recall,
Jean-Michel wrote:

[snip]

dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_claim_pages:151 - Memory cannot be moved
dynamicarea_claim_pages:151 - Memory cannot be moved

Do dynamicarea_map_pages correspond to dynamic area numbers?

Probably not - more likely these are error values of some sort?

It seems to me that all DA numbers are above 255.
Hariett, are you still using your ARMX6?

Yes, this is on an ARMX6.

Ok,

I'm looking at your Dynamic Areas tutorial for using DA in a program, very interesting because they are examples.

Rhapsody4 uses them for every score it creates.

I use the program !Virtualise by Alexander Thoukydides (without the
module). This allows me to check the DAs present.

Bonn journoe.
--
Jean-Michel
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

In message <f22693f25c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

On 2 Jul 2026 as I do recall,
Jean-Michel wrote:

[snip]

dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_claim_pages:151 - Memory cannot be moved
dynamicarea_claim_pages:151 - Memory cannot be moved

Do dynamicarea_map_pages correspond to dynamic area numbers?

Probably not - more likely these are error values of some sort?

It seems to me that all DA numbers are above 255.
Hariett, are you still using your ARMX6?

Yes, this is on an ARMX6.

I think the application that creates mmap#0 is !Muview after loading a PDF file.
The DA disappears after closing the file, but may not be deleted if Muview crashes ,
--
Jean-Michel
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

In message <f72ba1f75c.jmb@jmc.bruck.orange.fr>
Jean-Michel <jmc.bruck@orange.fr> wrote:

In message <f22693f25c.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

On 2 Jul 2026 as I do recall,
Jean-Michel wrote:

[snip]

dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_map_pages:240 - Bad page number
dynamicarea_claim_pages:151 - Memory cannot be moved
dynamicarea_claim_pages:151 - Memory cannot be moved

Do dynamicarea_map_pages correspond to dynamic area numbers?

Probably not - more likely these are error values of some sort?

It seems to me that all DA numbers are above 255.
Hariett, are you still using your ARMX6?

Yes, this is on an ARMX6.

I think the application that creates mmap#0 is !Muview after loading a PDF file.
The DA disappears after closing the file, but may not be deleted if Muview crashes ,

mmap#0 is used by several different programs, including !Iris
--
Chris Hughes
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

In message <abc8a5f75c.chris@mytardis>
Chris Hughes <news13@noonehere.co.uk> wrote:

I think the application that creates mmap#0 is !Muview after loading a PDF >> file.
The DA disappears after closing the file, but may not be deleted if Muview >> crashes ,

mmap#0 is used by several different programs, including !Iris

Ok,
If I open Iris and Muview at the same time, they share the same mmap#0.
--
Jean-Michel
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

On 13 Jul, Jean-Michel wrote in message
<462fd4f75c.jmb@jmc.bruck.orange.fr>:

In message <abc8a5f75c.chris@mytardis>
Chris Hughes <news13@noonehere.co.uk> wrote:

mmap#0 is used by several different programs, including !Iris

Ok, If I open Iris and Muview at the same time, they share the same
mmap#0.

Presumably it's something that comes from the porting tools, then?
--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

On 13 Jul 2026 as I do recall,
Jean-Michel wrote:

In message <abc8a5f75c.chris@mytardis>
Chris Hughes <news13@noonehere.co.uk> wrote:

I think the application that creates mmap#0 is !Muview after loading a PDF >> file.
The DA disappears after closing the file, but may not be deleted if Muview >> crashes ,

mmap#0 is used by several different programs, including !Iris

Ok,
If I open Iris and Muview at the same time, they share the same mmap#0.

I have Iris running at the moment and don't have Muview on the computer,
and I've got an mmp0 and an mmap1 showing! :-)
--
Harriet Bazley == Loyaulte me lie ==

Nothing is foolproof - to a sufficiently talented fool
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.apps

Steve Fryatt <news@stevefryatt.org.uk> wrote:

On 13 Jul, Jean-Michel wrote in message
<462fd4f75c.jmb@jmc.bruck.orange.fr>:

In message <abc8a5f75c.chris@mytardis>
Chris Hughes <news13@noonehere.co.uk> wrote:

mmap#0 is used by several different programs, including !Iris

Ok, If I open Iris and Muview at the same time, they share the same
mmap#0.

Presumably it's something that comes from the porting tools, then?

mmap might be related to the Unix mmap() system call (meaning 'memory map'): https://en.wikipedia.org/wiki/Mmap

It's possible that a shared library used by both Iris and Muview is using mmap() to allocate memory for its clients, and it's allocating it in the
same dynamic area. Perhaps each time something creates an mmap() region a
new mmap#N dynamic area is created?

One thing that mmap() can do is reserve an address space where not all the memory is allocated, eg you can ask for 1GiB of contiguous address space without needing to have 1GiB of available RAM, and the memory only gets populated bit by bit when you actually use it. On RISC OS this isn't
possible in application space but is in 'sparse' dynamic areas, which might
be why apps need to use a separate DA instead of just keeping it in their application slot.

Theo
--- Synchronet 3.22a-Linux NewsLink 1.2