SIGSEGV when creating tables from Dataframes (only on Laptop)

[noafilou]

What happens?

When i try to run the following example i run into a SIGSEGV.

I get this error:
Process finished with exit code 139 (interrupted by signal 11:SIGSEGV)

It only happens on my Laptop - on my Desktop i can run the exact same thing and it just works.
My Desktop runs the exact same OS, Version, Architecture and Virtual (uv) Environment.
And it happens across Data Sets. I did the same thing with completely unrelated excel files.

Any ideas why this happens?

My RAM doesn't spike, and it idles around 56% while running it so i don't think thats the problem here.

To Reproduce

import duckdb
import polars as pl

df = pl.DataFrame("test")
with duckdb.connect() as con:
    con.sql(f"DROP TABLE IF EXISTS test")
    con.sql(f"CREATE TABLE test AS SELECT * FROM df")

Additional Information

This code works (taken from your docs) - so it seems to be the Dataframe to Table conversion:

#df = pl.DataFrame("test")
with duckdb.connect() as con:
    #con.sql(f"DROP TABLE IF EXISTS test")
    con.sql(f"CREATE TABLE test AS SELECT 42 a")

OS:

PopOS 24.04. x86_64

DuckDB Package Version:

1.5.4

Python Version:

3.13.7

Full Name:

I'd rather not

Affiliation:

I do not work for a Company, i write Hobby Open Source Software.

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration to reproduce the issue?

• Yes, I have

[noafilou]

Further Investigations

I nailed this Issue down to my PyCharm-Setup, because when i run the script in the Terminal with uv run script.py it runs just fine.

I use PyCharm 2026.1
For now, i don't know yet what the problem may be - could be the cache, could be the "interpreter", ...

It cant be the dependencies, since it uses the same virtual environment.

I suppose this is out of scope now, so feel free to close it.

[evertlammerts]

Thanks for the report! If it turns out to have something to do with duckdb, then feel free to file a new issue.