it only shows components when they're using enough resources to register. for example, i only see foo_uie_esplaylist.dll when scrolling through my library for the first time as it loads all cover images. this causes a little cpu load but as soon as i stop, it goes away again.

you could try a portable foobar install without additional components. configure it to monitor the same music folders as your normal install and also configure your usual autoplaylists. now check the memory usage of the barebones install and you'll see what effect your 3rd party components are having.

it's probably not worth bothering with though. i'm sat here typing this into firefox which is using 200MB with one tab open and this website isn't exactly content heavy. do i care? not one bit.

You can create a close approximation of a built-in memory analysis tool for foobar2000 by doing this:

Create and add a toolbar button named "Run VMMap" to your fb2k layout. If the button is clicked, an external program named "VMMap" is launched with command line parameter like this: vmmap.exe foobar2000.exe .

In this screenshot, I am running a brand new install of foobar2000 with only one added component "foo_wave_seekbar.dll" and one playlist...and I added a toolbar button to the layout ("Run VMMap"):

In this screenshot, you can read detailed info about VMMap:

In this screenshot, foobar2000 is running and playing a track, and i have clicked on the "Run VMMap" button at the toolbar ...and VMMap pops up with the specified command line:

So there you have it; a memory analyzer tool built into foobar2000 using a 'QuickLaunch' type button .

Looking at your list of components at Post #8, I assume you are using the Columns UI interface.If so, you are in luck because you can make a button in Javascript using the WSH Panel Mod component.Columns UI allows you to add WSH Panel Mod elements to the toolbar. Default UI does not allow this feature!.

To have this button in DUI, you need to create a DLL component; at present it does not exist ...but stay tuned

Think, it's too much trouble for me creating this button. Partly because I have no knowledge of wsh panel coding and partly because I'm probably not going to use it. I'll be fine with launching VMMap manually from its folder.

Sorry to disappoint you but that is not even a close approximation of something that could be called memory usage of a component. What looks like the memory usage is only the image file. That means the executable program (i.e. the dll file more or less). The memory that a component requests is in the category "Heap" which is not split by dlls.