[Invaliderror]

I’m seeing the message every now and then both on my PC and the tablet I’m using as the extra screen even when there is nothing displayed on the Spacedesk screen and network bandwidth on my PC is ~40kbps. Even when Spacedesk complains about bandwidth while I am using the extra screen, I’m not noticing any performance issues.

To me, it feels like the warning is most frequently getting tripped when the Spacedesk screen hasn’t been updated in a while, such as when I’m done reading a page and start scrolling down or proceed to the next page. My guess is the warning threshold is so low that Spacedesk complains about „low bandwidth“ simply because the tablet and possibly the router’s WiFi have gone into a power-saving state and are taking slightly too long to respond for Spacedesk’s liking.

Since all „low bandwidth warnings“ I’m seeing appears to be spurious, I’d like to simply have an option on Windows and Android to silence low bandwidth warnings or some way to raise the threshold that triggers the warning, ex.: give the client-server connection X seconds to clear its backlog before complaining about a slow connection.

[Invaliderror]

When I don’t use SpaceDesk, my PC runs fine 3-4 months at a time between manual reboots for system and driver updates.

I don’t have a minidump folder as the system never outright crashed. It ran out of memory which caused programs to crash and the system to become unusable but still running. It was the first time I have seen an „out of memory“ error in 10+ years.

I just went through my Event Logs, found a huge blob of service failures on 2022-04-02 which must be when the quasi-crash happened and mixed in there, I have a Resource Exhaustion Detector event stating the following:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: spacedeskService.exe (6624) consumed 15600336896 bytes, Wow.exe (23148) consumed 7649738752 bytes, and soffice.bin (10900) consumed 1279406080 bytes.

At the very least, something definitely caused virtual memory allocation to go completely nuts. I rarely play WoW for more than 3-4h at a time and it somehow got to 7TB of virtual memory too.

[Invaliderror]

Getting to the crash takes a few weeks of actively using the remote screen a few hours per day without restarting SpaceDesk. The 17TB in my screen cap was about a week after updating to 0.46. Between the timing and the tendency of most computer things aligning with powers of two, I’m guessing the out-of-memory system collapse happens at either 32TB or 64TB on my setup. The system runs out of physical memory tracking virtual memory that gets allocated on every screen update but never actually used.

Technically, the system didn’t quite crash back then. The OS terminated processes left and right to free up memory and put the system in an unusable state where attempting to do anything resulted in out-of-memory errors until enough of whatever was still running got OoM-crashed on shutdown to free up memory for the remainder to shut down normally.

Attachments:

You must be logged in to view attached files.

[Invaliderror]

I have tried „Save All Information“ three times and the designated output folder remains empty even after installing DebugView, running debug mode for the few seconds it takes to get 20GB of „Dedicated video memory“ by wiggling a window on the remote display and turning it back off before clicking the button.

If it is a systemic problem, it shouldn’t take more than a few seconds to duplicate:
1- connect a remote display
2- open Task Manager in detail view showing dedicated GPU memory
3- wiggle a window on the remote display
4- watch the dedicated GPU memory rise by ~1GB/s for as long as the window is being wiggled on the remote display

The first time my computer mysteriously crashed from running out of memory was about a year ago. Whatever the issue might be, it isn’t a recent development.

I found DebugView’s log where SpaceView dumped its unpacked copy. No activity in there beyond the initial display connection chatter.

Since it is a VRAM-related issue, it is likely worth mentioning that I am using a GTX1050.

Attachments:

You must be logged in to view attached files.

[Autor]

Beiträge