Windows Audio Endpoint Builder



  • @Ragnax said:

    Significant addendum; memory-mapped files or other types of streams are also deemed to be 'resident in physical memory', even though they do not take up RAM. Device memory, such as output buffers for audio devices can also be a part of this. And what does audio endpoint builder do? Right! It builds up a graph of endpoints which are associated with streams or buffers to which audio data can be written for playback.


    Yes, because it takes 150MB of pseudo-RAM to write nothing to a nonexistent audio card.



  • @Ben L. said:

    Yes, because it takes 150MB of pseudo-RAM to write nothing to a nonexistent audio card.

    The audio card probably does exist -- No doubt that there is a flaky on-board chipset present -- but the TS probably does not have any speakers or headphones plugged into the jacks.

    A badly written audio driver could quite possibly reach that amount of memory consumption, especially if you take into account that those 150MB may contain duplicated memory pages that point to the same memory space on the device. The private working set does not list physical memory usage. It lists virtual memory usage and multiple pages of virtual memory may be mapped to the same physical memory.



  • Talk about the Complicator's Gloves. 

    Fit more ram and be done with it, 4gb is cheap enough these days.


  • Discourse touched me in a no-no place

    @Ben L. said:

     

    Yes, because it takes 150MB of pseudo-RAM to write nothing to a nonexistent audio card.

     

     

    Were you not paying attention?  You can't say that.  Windows Audio Endpoint Builder shares a process with approximately 8 other services.  Right now, on my Windows 8 box, WAEB has PID 320, which also hosts Distributed Link Tracking Client, Network Connections, Program Compatibility Assistant Service, Remote Desktop Services UserMode Port Redirector, SuperFetch, Windows Driver Foundation - User-mode Driver Framework, and WLAN AutoConfig.  Do you think any of them, particularly, say, Network Connections or SuperFetch, could possibly be using any of that memory?


Log in to reply