Massive AUsb Nonpaged Pool Memory Leak with Android Digital Signage (USB Connection)
Quote from Kazushige on 22/11/2025, 08:16(Please forgive me if my English isn’t perfect; I used an AI tool to help write this message accurately. Thank you for your understanding!)
Hi Spacedesk Team & Fellow Users,
I’ve run into a serious memory leak issue when using the Spacedesk Android USB feature for a video wall setup. I’m hoping someone has seen this or the team can look into it, as it completely freezes my PC after a few days!
My Setup:
Host PC: Windows 11 (Up-to-date)Client Setup: I’m running a 3-screen video wall using Android Digital Signage displays connected via USB (not regular phones/tablets).
Usage: Continuous video loop playback (using PotPlayer) across all three screens.
The Problem: Giant Memory Leak
When running this setup for a few days, my PC’s RAM usage shoots up to 99%, leading to a total freeze.Using Windows tools (PoolMon and RamMap), I confirmed this is a Nonpaged Pool memory leak caused by the AUsb tag.
Leak Size: The AUsb tag alone was consuming over 10 Gigabytes (10.1GB) of the nonpaged pool. (I’ve attached screenshots from PoolMon showing the 10.1GB leak.)
The Culprit: The AUsb tag is strongly linked to USB/Virtual Audio Drivers, which makes sense given the spacedesk Android USB Device drivers shown in Device Manager.
What I’ve Tried:
Audio Output Switch: I thought it was an audio issue, so I forced the Windows audio output from Spacedesk to my HDMI port.Result: The leak did not stop. The AUsb tag continued to grow, meaning the problem is likely tied to the USB data transfer stack for the Android signage devices, not just the audio output itself.
My Request:
I believe there’s a bug in the Spacedesk driver’s handling of sustained USB data streamsHas anyone else encountered this problem, or can the Spacedesk team please investigate why the AUsb pool is filling up so massively when streaming video via USB to Android devices?
Thanks for any help or insight!
(Please forgive me if my English isn’t perfect; I used an AI tool to help write this message accurately. Thank you for your understanding!)
Hi Spacedesk Team & Fellow Users,
I’ve run into a serious memory leak issue when using the Spacedesk Android USB feature for a video wall setup. I’m hoping someone has seen this or the team can look into it, as it completely freezes my PC after a few days!
My Setup:
Host PC: Windows 11 (Up-to-date)
Client Setup: I’m running a 3-screen video wall using Android Digital Signage displays connected via USB (not regular phones/tablets).
Usage: Continuous video loop playback (using PotPlayer) across all three screens.
The Problem: Giant Memory Leak
When running this setup for a few days, my PC’s RAM usage shoots up to 99%, leading to a total freeze.
Using Windows tools (PoolMon and RamMap), I confirmed this is a Nonpaged Pool memory leak caused by the AUsb tag.
Leak Size: The AUsb tag alone was consuming over 10 Gigabytes (10.1GB) of the nonpaged pool. (I’ve attached screenshots from PoolMon showing the 10.1GB leak.)
The Culprit: The AUsb tag is strongly linked to USB/Virtual Audio Drivers, which makes sense given the spacedesk Android USB Device drivers shown in Device Manager.
What I’ve Tried:
Audio Output Switch: I thought it was an audio issue, so I forced the Windows audio output from Spacedesk to my HDMI port.
Result: The leak did not stop. The AUsb tag continued to grow, meaning the problem is likely tied to the USB data transfer stack for the Android signage devices, not just the audio output itself.
My Request:
I believe there’s a bug in the Spacedesk driver’s handling of sustained USB data streams
Has anyone else encountered this problem, or can the Spacedesk team please investigate why the AUsb pool is filling up so massively when streaming video via USB to Android devices?
Thanks for any help or insight!
Uploaded files:- You need to login to have access to uploads.
Quote from spacedesk Renz on 24/11/2025, 03:28Hi @kazushige,
For further analysis of the issue, please send us the logs of your Primary PC by opening the spacedesk Driver console as administrator and clicking on Diagnostics then follow the steps below:
1. Download the DebugView.
2. Check the Diagnostic Collection box.
3. Reproduce the issue e.g. by connecting the spacedesk Viewer app via USB.
4. Uncheck the Diagnostic Collection box.
5. Click “Save All Information” button (this might take a while to finish).
6. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If the folder exceeds 512kb, you may upload it to Dropbox or Google Drive then include the download link on your next reply.Thank you.
Hi @kazushige,
For further analysis of the issue, please send us the logs of your Primary PC by opening the spacedesk Driver console as administrator and clicking on Diagnostics then follow the steps below:
1. Download the DebugView.
2. Check the Diagnostic Collection box.
3. Reproduce the issue e.g. by connecting the spacedesk Viewer app via USB.
4. Uncheck the Diagnostic Collection box.
5. Click “Save All Information” button (this might take a while to finish).
6. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If the folder exceeds 512kb, you may upload it to Dropbox or Google Drive then include the download link on your next reply.
Thank you.
Quote from spacedesk Renz on 24/11/2025, 11:21Hi @kazushige,
We managed to reproduce this issue on our side. We will be able to start looking into this on and after December 2nd 2025.It will take some time and effort to analyze the root cause and fix it. We will keep you informed. In the meantime, please submit your diagnostic data we requested above. This might help us speeding up analysis. Thank you.
Hi @kazushige,
We managed to reproduce this issue on our side. We will be able to start looking into this on and after December 2nd 2025.It will take some time and effort to analyze the root cause and fix it. We will keep you informed. In the meantime, please submit your diagnostic data we requested above. This might help us speeding up analysis. Thank you.
Quote from Kazushige on 25/11/2025, 03:53Hi @spacedesk-renz,
That’s excellent news! Thank you very much for successfully reproducing the issue and scheduling the investigation.
I have collected the diagnostic data as requested. Since the compressed log folder exceeds the size limit (512KB), I have uploaded it to Google Drive.
Here is the download link: https://drive.google.com/file/d/11gIpjK2IvSOYUHNNLyxIf_T7gryGyFj5/view?usp=drive_link
I understand that a root cause analysis and fix will take time. I appreciate you keeping me informed after December 2nd.
Thank you again for your quick response and effort!
Hi @spacedesk-renz,
That’s excellent news! Thank you very much for successfully reproducing the issue and scheduling the investigation.
I have collected the diagnostic data as requested. Since the compressed log folder exceeds the size limit (512KB), I have uploaded it to Google Drive.
Here is the download link: https://drive.google.com/file/d/11gIpjK2IvSOYUHNNLyxIf_T7gryGyFj5/view?usp=drive_link
I understand that a root cause analysis and fix will take time. I appreciate you keeping me informed after December 2nd.
Thank you again for your quick response and effort!
Quote from spacedesk Renz on 25/11/2025, 04:02Hi @kazushige,
Thank you for sending a link for your diagnostic logs. May we request that you make the link public so we may check the logs? Thank you.
Hi @kazushige,
Thank you for sending a link for your diagnostic logs. May we request that you make the link public so we may check the logs? Thank you.
Quote from Kazushige on 25/11/2025, 15:29Hi spacedesk Renz,
I sincerely apologize for the confusion regarding the previous link’s sharing setting.
I have corrected the public sharing configuration on the Google Drive link.Please download the diagnostic logs from the updated URL below. Thank you for your patience.
https://drive.google.com/file/d/11gIpjK2IvSOYUHNNLyxIf_T7gryGyFj5/view?usp=drivesdk
Hi spacedesk Renz,
I sincerely apologize for the confusion regarding the previous link’s sharing setting.
I have corrected the public sharing configuration on the Google Drive link.
Please download the diagnostic logs from the updated URL below. Thank you for your patience.
https://drive.google.com/file/d/11gIpjK2IvSOYUHNNLyxIf_T7gryGyFj5/view?usp=drivesdk
Quote from spacedesk Renz on 01/12/2025, 07:41Hi @kazushige,
we have released a new spacedesk Driver Package v2.2.12 that contains the fix for the memory leak issue you encountered. Please install this new version and kindly verify if the issue is fixed on your end. Thank you.
Hi @kazushige,
we have released a new spacedesk Driver Package v2.2.12 that contains the fix for the memory leak issue you encountered. Please install this new version and kindly verify if the issue is fixed on your end. Thank you.
Quote from Kazushige on 02/12/2025, 13:27Thank you for the quick update.
I have installed the new v2.2.12 driver package, and I will now verify whether the memory leak issue has been resolved on my system.
I’ll report back with the results.
Thank you for the quick update.
I have installed the new v2.2.12 driver package, and I will now verify whether the memory leak issue has been resolved on my system.
I’ll report back with the results.
Quote from Pat on 03/12/2025, 13:17The AUsb nonpaged pool leak looks serious. Continuous USB data streaming might be overwhelming the driver. Hopefully the Spacedesk team can replicate and patch this issue soon.
The AUsb nonpaged pool leak looks serious. Continuous USB data streaming might be overwhelming the driver. Hopefully the Spacedesk team can replicate and patch this issue soon.
Quote from mathewwade on 04/12/2025, 15:43I’m seeing the same thing happening with the spacedesk Android‑USB display feature. The memory leak under the “AUsb” nonpaged pool after a few days of continuous USB streaming is a serious issue. I hope the spacedesk development team will prioritize this bug, since a 10 GB nonpaged‑pool leak is enough to freeze the PC. Meanwhile I’ll also test and share logs if needed.
I’m seeing the same thing happening with the spacedesk Android‑USB display feature. The memory leak under the “AUsb” nonpaged pool after a few days of continuous USB streaming is a serious issue. I hope the spacedesk development team will prioritize this bug, since a 10 GB nonpaged‑pool leak is enough to freeze the PC. Meanwhile I’ll also test and share logs if needed.