-----Original Message-----
From: ros-dev-bounces(a)reactos.com
[mailto:ros-dev-bounces@reactos.com] On Behalf Of Ge van Geldorp
Sent: Sunday, October 03, 2004 1:20 AM
To: 'ReactOS Development List'
Subject: RE: [ros-dev] TEB spacing
From: Ge van Geldorp
> From: Hartmut Birr
>
> I've still more problems with the modifications in the virtual
> memory functions. My test case is ctm from rosapps. It
shows the cpu
> time and memory usage of the processes.
While waiting for
a keyboard
event,
ctm
(kernel32) destroys and creates every 100ms a new thread. It
seems, that the memory (teb, stack, ...) isn't freed. The
thread itself is destroyed. Ps
shows always two threads for ctm.
Ok, I'll dig into it to see what's wrong.
Are you sure the behaviour changed recently? What I see is
that the TEBs are properly freed, but the stack (2Mb of
committed memory) isn't. That happens because the threads
don't terminate themselves, but are terminated using
TerminateThread(). If a thread calls ExitThread() then its
stack is freed, but if a thread is ended using
TerminateThread(), its stack is not freed.
It still needs to be fixed ofcourse, but I'm wondering what
my recent changes have to do with this.
Ge van Geldorp.
Hi,
I'm not sure if all of my problems from ctm are related to your changes.
After the first problem I've do more testing with ctm. In the past I've used
one console for buildung ros and another which runs ctm. I've build ros
completly. Currently I've get a bugcheck (my first reported problem which is
now fixed) in the teb allocation routines and now I'see that ctm eats up all
available memory.
- Hartmut