• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Giorgi / DuckDB.NET / 35860865834
88%

Build:
DEFAULT BRANCH: develop
Ran 23 Sep 2026 12:33PM UTC
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
35860865834

push

github

Giorgi
Refresh nested writers when a list of arrays grows

When a list outgrows its space in a batch, ListVectorDataWriter reserves
more room and refreshes its item writer's pointers. DuckDB's
Vector::Resize also moves the items of any ARRAY inside the list,
because an array's item buffer is always its capacity times the array
size. Only the direct item writer was refreshed, so for a list of arrays
the array's own item writer kept writing to the freed buffer.

Every array written after the list grew was lost, and in the test host
the writes into freed memory crashed the process, with or without NULLs.
Lists of lists were unaffected, because DuckDB leaves a list's items in
place when the outer list grows.

InitializeWriter is now virtual, and ListVectorDataWriter overrides it
to refresh its item writer too, so the refresh reaches every nested
level. For writers whose buffers did not move, it re-reads the same
pointer.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KxGp85FzaVDRPo7eXVBFrf
Source Files on build 35860865834
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #35860865834
  • 7dc9f6eb on github
  • Prev Build on develop (#35847999295)
  • Next Build on develop (#35915328756)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc