RE: Mozilla eats even more memory

["Anderson, Tim TL33E" <Tim.Anderson@ace-ina.com>]

	> If they are threads then this would be a (serious?) bug in the
graphical
	> top-like tool I used.
	> 
	>t's not a bug, it's a feature! ;-)
	>under linux, threads are equivalent processes. the only difference
between
	>them and real processes is, that threads belonging to one program
share 
	>their memory. currently there is no means of finding out, which
threads 
	>belong together (aside from looking deep into system data
structures).
	>a new feature called "thread groups" has been introduces into the
upcomming 
	>2.4 kernel a few weeks ago (or at least it has been discussed).
this was
	>done with posix threads in mind, but will also enable simpler
recognition 
	>of threads belonging together in top-like programs.

	>i hope, this clarification does not confuse you even more ... :)
	
	--------------------
	Right, so it's not a bug in my top-like program, just a bug in the
kernel :-)
	Mind you, if the memory space is always identical (surely position
as well as size) 
	then why is it difficult to find shared threads?   Very naïve of me
I know, but surely
	you don't need to go too deep into the system to find the base
address of a process.

	tim