#RE2 feature flags don't work on Windows - CrowdSec crashes

1 messages · Page 1 of 1 (latest)

solid zealot
#

Hi,

Tested RE2 flags on Windows Server (2012 R2 through 2025) with versions 1.6.11 and 1.7.3.

Observed behavior:
re2_grok_support: Crashes right after "Loading grok library" (no error)
re2_regexp_in_file_support: Crashes after loading postoverflow parsers (no error)

Logs stop at:
v1.7.3 + re2_grok_support:
→ "Loading grok library C:\ProgramData\CrowdSec\config\patterns" [HANG]

v1.7.3 + re2_regexp_in_file_support:
→ "Loaded 1 parser nodes" (postoverflows/s01-whitelist) [HANG]

Without the flags, everything works perfectly.

Are RE2 flags supposed to work on Windows?
Is this a known issue with WASM/wazero on Windows?

rotund forumBOT
#
Important Information

Thank you for getting in touch with your support request. To expedite a swift resolution, could you kindly provide the following information? Rest assured, we will respond promptly, and we greatly appreciate your patience. While you wait, please check the links below to see if this issue has been previously addressed. If you have managed to resolve it, please use run the command /resolve or press the green resolve button below.

Log Files

If you possess any log files that you believe could be beneficial, please include them at this time. By default, CrowdSec logs to /var/log/, where you will discover a corresponding log file for each component.

Guide Followed (CrowdSec Official)

If you have diligently followed one of our guides and hit a roadblock, please share the guide with us. This will help us assess if any adjustments are necessary to assist you further.

Screenshots

Please forward any screenshots depicting errors you encounter. Your visuals will provide us with a clear view of the issues you are facing.

tough bough
#

Hello,

I saw that a while ago, the issue is not specific to windows, I encountered this on linux as well.

I haven't took the time to investigate properly yet, as it's a bit of a niche situation (majority of the users are on linux, and we default to a native re2 implementation here which does not have the issue).