I would think the application developer has control over this.Ed said:There's a column heading in Task Manager Processes for "Threads". You
get to it from Processes, View, Select Columns.
Well, every single process (maybe I should have written "every
individual process") has several threads; not a one below 2.
At present the highest is NT Kernel & System, with 137; ...... Firefox
with 45,................ Tbird with 29, ............ lastly Windows
Session Manager with 3.
I just opened another tab in Firefox, went to a big site, and the Thread
count went up before my eyes to 48; opened two more tabs plus data, ...
up to 49. Then I cut the tabs down to just the original one, and lo! it
stayed with 49.
Does this mean that every individual program there is hard-coded to
handle multi-threading? Or is Win7 itself handling it, in the same way
it handles paging to swapfiles? Firefox isn't releasing memory too well.
Who should I blame, MS or the FF people?
They should be able to terminate a thread, and clean up the
resources. If the OS didn't support resource cleanup, then
the OS would not be "scalable".
It's possible Firefox has some arbitrary criteria, as to when it
cleans up after itself. With 64000 source files, good luck finding
the source code that does it. (Source code is available on the
Mozilla site, if you want it. It takes two solid days of work, to
compile your own copy.)
It's possible an integrated development environment, can accept
relatively simple source code (no threads evident), and still
produce a program that uses threads. Things like perhaps a
GUI, might have its own thread of execution. So some of the
threads you're seeing, may not have been hand-crafted. But
something like Firefox, with 45, is likely to be doing
its own threads for stuff. And Firefox would be running
instances of SQLite, and those would need to run independently
for the database functions Firefox uses. Modern browsers also
use process isolation, and that means more independence at
runtime (each window is its own instance, and can die without
killing the whole thing). At least, that's the theory.
Mozilla used to have a web page, dedicated to complaints about
their memory usage. So they know about it
Now, an interesting feature there, is type this into the address bar.
That should be good for a laugh.
And this page, is their own page for the developers to find problems.