Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

SEGFAULT (0xC0000005) on Windows x64 when executing LOAD VECTOR

Abierto
  • ¿Algo no está bien?
#499 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
cpp, node.js
Área
databases, operating-systems

Línea de trabajo

Start by running the provided test.mjs on Windows x64 to reproduce the deterministic crash. Trace initLbug() through doInitLbug() and loadVectorExtension(), focusing on the VECTOR extension's native initialization and Windows loading path. Done means LOAD VECTOR no longer terminates the Node.js process, with the chosen behavior verified for the database when extension loading fails.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

LOAD VECTOR triggers a native access violation (segfault) on Windows x64, crashing the entire Node.js process. INSTALL VECTOR succeeds, but LOAD VECTOR immediately causes STATUS_ACCESS_VIOLATION (0xC0000005).

Environment

Item Value
OS Windows 11 x64
Node.js v22.15.0
@ladybugdb/core 0.15.4
lbugjs.node 13,227,008 bytes
CPU (available on request)

Reproduction

// test.mjs — place inside any project with @ladybugdb/core installed
import lbug from '@ladybugdb/core';
import fs from 'fs/promises';
import path from 'path';

const dbPath = './test.lbug';
await fs.mkdir(path.dirname(dbPath), { recursive: true });

const db = new lbug.Database(dbPath);
const conn = new lbug.Connection(db);

// This works fine
await conn.query('CREATE NODE TABLE Test (id STRING, PRIMARY KEY(id))');
console.log('Schema OK');

// This works fine
await conn.query('INSTALL VECTOR');
console.log('INSTALL VECTOR: OK');

// This crashes the process with 0xC0000005
await conn.query('LOAD VECTOR');
console.log('This line is never reached');

await conn.close();

node test.mjs
# Output:
# Schema OK
# INSTALL VECTOR: OK
# LOAD VECTOR...
# <process exits with code -1073741819>

Exit code -1073741819 = 0xC0000005 = STATUS_ACCESS_VIOLATION.

Isolation Tests

All of the following work without any crash:

Test Result
require('@ladybugdb/core') native addon load ✅
new lbug.Database(path) ✅
new lbug.Connection(db) ✅
33 schema creation queries (tables, indexes, etc.) ✅ all pass
INSTALL VECTOR ✅
LOAD VECTOR 💥 SEGFAULT
tree-sitter native + @ladybugdb/core co-loaded ✅
onnxruntime-node + @ladybugdb/core co-loaded ✅

The crash is deterministic and occurs on every LOAD VECTOR call, regardless of:

  • Database content (empty or populated)
  • Other native addons loaded before/after
  • --max-old-space-size or --stack-size Node.js flags
  • Working directory or path length

Downstream Impact

This crash makes gitnexus analyze completely unusable on Windows, because gitnexus calls initLbug() → doInitLbug() → loadVectorExtension() → conn.query('LOAD VECTOR') during every repository indexing operation.

GitNexus issue: (pending)

Suggested Fix

  1. Investigate the VECTOR extension's native initialization on Windows x64 — likely an uninitialized pointer, missing SIMD fallback, or DLL dependency issue in the extension loading path.
  2. As a workaround, consider making VECTOR extension loading optional/catchable so that the database remains usable (without vector search) even if the extension fails to load.
Lenguaje dominante
C++
Estrellas
1.8k
Forks
148
Merge medio
14 h 57 min
PR fusionados (30 d)
124

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de LadybugDB/ladybug

Todos los issues de LadybugDB/ladybug

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.