New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core dump when calling the list
aggregate function.
#9949
Comments
Hi @yiyuanliu, this query completed on my MacBook Pro (32GB RAM). |
The machine architecture is x64, containing 2 NUMA nodes with a total of 128 physical cores. My testing was carried out inside a container configured with 32 CPU cores and 64GB of memory. Under the default configuration of DuckDB, the number of threads is also set to 32 cores. |
This query also crashed on my MacBook Pro(M1 pro, 16GB RAM). It appears that the query itself executed successfully, but an incorrect memory address was accessed when converting the result to string for output.
|
What happens?
To Reproduce
see above
OS:
ubuntu 2204
DuckDB Version:
v0.9.3-dev1411 7d5150c
DuckDB Client:
cli
Full Name:
Yiyuan Liu
Affiliation:
High-Flyer AI
Have you tried this on the latest
main
branch?I have tested with a main build
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: