Reading parquet using DuckDB

[andrejfg]

How can we reproduce the crash?

Read sequentially many parquet files using DuckDB

JavaScript/TypeScript code that reproduces the crash?

I cannot

Relevant log output

🦊 Elysia is running at http://localhost:3001
============================================================
Bun v1.1.8 (89d25807) Windows x64
Args: ":\\sers\\ndrGuimares\\bun\\in\\un.exe", "run", "--watch", "src/index.ts"
Features: jsc dotenv http_server tsconfig_paths(2) tsconfig(12) 
Builtins: "bun:main" "detect-libc" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:os" "node:path" "node:stream" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:http2" 
Elapsed: 740ms | User: 312ms | Sys: 140ms
RSS: 0.37GB | Peak: 0.37GB | Commit: 0.47GB | Faults: 94699

panic(main thread): Segmentation fault at address 0x101080208
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

--- Bun is auto-restarting due to crash [time: 1716326891428] ---

Stack Trace (bun.report)

Bun v1.1.8 (89d2580) on windows x86_64 [RunCommand]

Segmentation fault at address 0xFFFFFFFFFFFFFFFF

• napi_set_property
• ??? at 0x1af9c in duckdb.node
• ??? at 0x1c154 in duckdb.node
• ??? at 0x63ae in duckdb.node
• ??? at 0x8012 in duckdb.node
• napi.zig:1147: runFromJS
• event_loop.zig:1268: tickConcurrent
• bun_js.zig:349: start
• JSC__VM__holdAPILock
• shimmer.zig:186: cppFn

[Delapouite]

A related issue regarding DuckDB has been fixed recently : https://github.com/oven-sh/bun/issues/13836 Does it also solve your problem?