Stack overflows
hey folks, I'm very consistently able to crash typedb 3.7.2 by simply testing my app with a very low volume of transactions
this is the summary from Claude but without more extensive logs which as far as I know I can't activate in the docker, I'm at a loss as to WHAT caused it
Summary:
Crash cause: TypeDB 3.7.2 internal bug - tokio-runtime-worker stack overflow
Trigger: Simple list_graph query (just listing entities, no relations)
Time: ~23:57:30, then again ~23:57:57 on restart
Status: TypeDB auto-recovered and is stable now
I was simply using an instance of Claude Code connected through the mcp server of my app planning an app (test run) and it was doing basic insertions and lists... at some point it stopped being able to process info and hiccupped.
You might want to report this to TypeDB - stack overflow on a basic match query is concerning. Could be related to:
Running for extended period (15+ hours)
Memory pressure
Specific data pattern triggering deep recursion in query planner
bottom line, give me better logging and I'll be able to help you a lot more
this is the summary from Claude but without more extensive logs which as far as I know I can't activate in the docker, I'm at a loss as to WHAT caused it
Summary:
Crash cause: TypeDB 3.7.2 internal bug - tokio-runtime-worker stack overflow
Trigger: Simple list_graph query (just listing entities, no relations)
Time: ~23:57:30, then again ~23:57:57 on restart
Status: TypeDB auto-recovered and is stable now
I was simply using an instance of Claude Code connected through the mcp server of my app planning an app (test run) and it was doing basic insertions and lists... at some point it stopped being able to process info and hiccupped.
You might want to report this to TypeDB - stack overflow on a basic match query is concerning. Could be related to:
Running for extended period (15+ hours)
Memory pressure
Specific data pattern triggering deep recursion in query planner
bottom line, give me better logging and I'll be able to help you a lot more
