[Bug]: I tested version 1.10.0.

[Afton-programmer]

Search existing issues

• I have searched the existing issues

Describe the bug

I tested the version that was emailed to me, but saving didn't work on Windows 10; it threw a timeout error. I don't have a dedicated graphics card, and my system specs are a 6th-gen Core i3 processor, a 500GB SSD, and 16GB of RAM.
What could be the reason for that?

Expected behavior

. . .

To Reproduce

No response

Screenshots

No response

OS

Windows

OS Version

windows 10

Other OS

No response

Browser

Chrome

Browser Version

No response

Other Browser

No response

Device Type

Laptop

Other Device

No response

Additional context

No response

[EtienneLescot]

Thanks for testing. This looks like it could be a different case from the GPU cross-device sync issue rc.1 mostly targets (#252) — your machine has no dedicated GPU, so recording falls onto the software H.264 encoder path, and its Finalize() step is known to be slow on weaker CPUs (that's why the stop timeout is 60s, up from 15s originally).

Can you reproduce it once more and send the helper's diagnostic log? It reports which encoder path was used and where the stop got stuck — that'll tell us whether this is the same GPU-sync bug or the software-encoder-finalize case, which would need a different fix (e.g. raising the timeout further for no-GPU machines).

[EtienneLescot]

For what it's worth, I can't reproduce this on my own low-end laptop — recording and export both work fine there:

• ASUS Vivobook Go E1404FA
• AMD Ryzen 5 7520U (4 cores / 8 threads, 2.8 GHz)
• Integrated AMD Radeon 610M only, no dedicated GPU (driver 32.0.11038.3)
• 16 GB RAM, SSD
• Windows 11 24H2 (build 26200), 64-bit

So an iGPU-only machine isn't the problem by itself. Your 6th-gen Core i3 is quite a bit older though, so it could be an encoder capability difference on Windows 10. If you can share the app logs from a failed export, that would help narrow it down.

[itsman212-droid]

Hello, I am experiencing the same problem on Windows 10.

When I stop a recording in OpenScreen, I receive this message:

Timed out waiting for native Windows capture to stop. The recording could not be saved.

My hardware is:

CPU: Intel Core i5-4590 @ 3.30 GHz

GPU: Intel HD Graphics 4600 (integrated graphics )

Windows: Windows 10

OpenScreen: v1.9.6

I also tested the v1.10.0-rc.2 build, but the recording still failed to save with the same timeout message. I tested short recordings as well, but the problem remained.

There is no dedicated NVIDIA or AMD GPU in my system. Another screen-recording application, cap.so, records and saves videos correctly on the same computer, so the issue does not appear to be caused by a general Windows screen-recording or disk-writing problem.

Could you please advise whether this is related to the software H.264 encoder or to the encoder-finalize / video-writer-join stage? I can provide diagnostic logs if you tell me where OpenScreen stores them and which files should be attached.

Please let me know if you need any additional information, such as the exact Windows build, graphics driver version, or a diagnostic report.

Thank you for your work on OpenScreen.