isaacbrodsky / h3-duckdb

Bindings for H3 to DuckDB
Apache License 2.0
173 stars 9 forks source link

Crash when loading on Windows Server #122

Closed szarnyasg closed 2 months ago

szarnyasg commented 3 months ago

I ran into a crash when loading H3 on Windows Server 2022, running on an r6i.4xlarge EC2 instance (16 Intel Xeon cores, 128 GB RAM). To reproduce, run the DuckDB v1.0.0 CLI client:

C:\Users\Administrator\Downloads\duckdb_cli-windows-amd64>duckdb -cmd "install h3 from community; load h3;"

C:\Users\Administrator\Downloads\duckdb_cli-windows-amd64>echo %errorlevel%
-1073741819

The output doesn't contain anything but the error code (which is consistently the same).

marklit commented 3 months ago

The above worked for me on Windows 11 so Windows Server might be different enough to warrant its own testing and not great for uncovering Windows 11 issues.

isaacbrodsky commented 3 months ago

Does Windows report that the process crashed? If so, it would be really helpful if you could attach a debugger and find where the crash happens.

I presume everything works OK if the SQL you run is anything other than load h3?

AntoineGiraudKeyrus commented 2 months ago

Hi,

Same issue on Windows 11 it just crash after load h3;

how may i attach debugger to give you more feedback ?

image

AntoineGiraud commented 2 months ago

ps: tried from an other windows 11 computer ... worked fined there ! 🧐 i'll try to reset duckdb on my 1st windows pc & install again h3

PS: congrat's for this great library, can't wait to use it on a side projet on Montreal's bikeshare data 😎

AntoineGiraud commented 2 months ago

Problem solved 🦆🚀

thanks to Microsoft Visual C++ Redistributable update cf. https://github.com/duckdb/duckdb/issues/13848#issuecomment-2343817545

carlopi commented 2 months ago

Hi all, this is a variation of this bug: https://github.com/duckdb/duckdb/issues/13848.

I tried to write down what happened and how it can be workarounded or fixed at: https://github.com/duckdb/duckdb/issues/13848#issuecomment-2352674000

If we had connected the dots earlier that might have saved some bugs report, BUT, good thing is that now we know what happened AND how to fix it.

I rebuilt h3 and I am double checking if any other community extension needs rebuilding, but I would consider this solved moving forward.

szarnyasg commented 2 months ago

This is resolved with v1.1.1, so closing this.