3.1.1 Windows binary does not run

[ggrothendieck]

The only way I can run recent versions of qsv on
Windows Version 10.0.19045.5487 is to build it myself using cargo.
The versions that do not work do not give any output when running qsv or
qsv --version and I assume for all else as well.

• qsv-0.125.0 mscv qsv.exe binary works
• qsv-3.1.1-x86_64-pc-windows-gnu.zip qsv.exe binary does not work
• qsv-3.1.1-x86_64-pc-windows-msvc.zip qsv.exe binary does not work
• building qsv 3.1.1 using cargo to build qsv does work

I have also previously tried some (not all) earlier releases than 3.1.1 and of
the ones I tried they do not work unless I build them using cargo. The 3.1.1
cargo build takes over 3 hours on my Windows laptop so I have to run it
overnight. I did not use optimization to build it.

Just to check that it is not everything that uses rust I tried to run the
csvlens 0.12.0 binary (i.e. not using cargo). This was released just a few days
ago and I had no problem so the problem seems specific to qsv.

[jqnatividad]

I have very limited access to Windows and I depend on GH Actions Windows runners to build them.

Currently, the Windows publishing workflows have CPU optimizations enabled, and they may prevent them from running on your Windows laptop.

What kind of Windows platform do you have? Is it Intel? AMD? What does systeminfo say when run from the command line? For it to take 3 hours tells me its a bit dated as the GH Windows runners take 35 minutes to build qsv, and they're low-specced (4 processors x64, 16gb RAM, 14 GB storage).

qsv has a ton of dependencies and uses a lot of SIMD crates that have CPU dependencies for performance.

Have you tried running the "portable" versions of qsv? (ending with the p suffix) when you download the binary archives? The "portable" versions do not have CPU optimizations enabled and should run on all Windows platforms.

[ggrothendieck]

One question. If I run this how can I determine which version was downloaded before running cargo.

git.exe clone https://github.com/dathere/qsv.git

This is the first few lines of systeminfo.

Host Name:                 X202E
OS Name:                   Microsoft Windows 10 Home
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Microsoft
Registered Organization:   Microsoft
Product ID:                00326-10000-00000-AA422
Original Install Date:     9/23/2021, 3:38:35 AM
System Boot Time:          2/22/2025, 9:58:22 AM
System Manufacturer:       ASUSTeK COMPUTER INC.
System Model:              X202E
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~1801 Mhz
BIOS Version:              American Megatrends Inc. X202E.208, 2/4/2013
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-ca;English (Canada)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory:     3,982 MB
Available Physical Memory: 1,185 MB
Virtual Memory: Max Size:  16,008 MB
Virtual Memory: Available: 9,723 MB
Virtual Memory: In Use:    6,285 MB

[jqnatividad]

In the same directory where you have qsv cloned, to fetch the latest:
git.exe pull

To find out what branch you're on.
git.exe status

Your machine is seriously underpowered for compiling Rust. It has a very old processor with very limited memory. I'm surprised it worked at all.

It may also be the reason why qsv is quitting before it's fully loaded since you only have so much usable memory after Windows is loaded.

I wouldn't use full-featured qsv if you don't need any of the optional features. I would just go with qsvlite.

[jqnatividad]

Converting this to a discussion as its not strictly a "bug".

[datatraveller1]

I've just downloaded qsv-3.1.1-x86_64-pc-windows-msvc.zip and the extracted qsv.exe binary does work perfectly on my Windows 11 PC and all my other laptops (Intel and AMD, Windows 10 and Windows 11):

C:\test\qsv>qsv --version
qsv 3.1.1-mimalloc-apply;fetch;foreach;geocode;Luau 0.660;prompt;to;polars-0.46.0:py-1.23.0;self_update-8-8;4.75 GiB-1.7
5 GiB-2.29 GiB-5.94 GiB (x86_64-pc-windows-msvc compiled with Rust 1.85) prebuilt

C:\test\qsv>

@ggrothendieck I'm sorry but I assume your specific PC has a problem. Can you try it on another Windows machine?

[jqnatividad]

Added a note about "portable" binaries...

2cec92a

[ggrothendieck]

I tried the qsv 3.1.1 msc release on another Windows PC but it had the same response which is that it just returns to the cmd line after entering qsv or qsv --version. With qsv 0.125.0 msc it did work properly. Maybe it only works on Windows 11?

[jqnatividad]

What does systeminfo say on the new machine?

Can you also run wmic cpu get name?

[ggrothendieck]

Tried more things. qsvplite.exe --version works on 3.1.1 but I get a virus protection error. No luau or polars with that. So far it is still the case that 0.125.0 is the only version of the ones I have tried that lets me run qsv.exe unless I use cargo. Haven't actually gotten 3.1.1 to work with cargo yet but will try again to build it overnight now that I have cmake installed.

BTW, I noticed that nushell, which is also written in rust, has multiple architecture versions for Windows and if I try to run the wrong one it fails. Maybe that has something to do with it.

nu-0.102.0-aarch64-pc-windows-msvc.zip
nu-0.102.0-x86_64-pc-windows-msvc.zip

[jqnatividad]

Can you share what qsvplite --version says?

Also, can you share what systeminfo and wmic cpu get name says?

This will help diagnose the problem.

[ggrothendieck]

Hi, Sorry but I deleted it as Windows was giving me virus warnings about Bearfoos virus on qsv-3.1.1-*.zip. I think you are right that I need to do this on a better PC so I am going to put this aside for the moment. qsv seems very powerful but maybe I can do with something less given that most of my computing is with R.

[ggrothendieck]