lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(wolf): checkpoint buglog.json (1026 bugs)

Browse source
This commit is contained in:
Rongsong Shen 2026-08-25 08:00:03 +00:00
parent e5e6cd1817
commit 307f5b82e1
No known key found for this signature in database
GPG key ID: 5BCDAAE0123E9FE2
1 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
.wolf/buglog.json
View file

@ -18715,6 +18715,25 @@
"related_bugs": [],
"occurrences": 1,
"last_seen": "2026-08-25T00:50:00Z"
},
{
"id": "bug-1685",
"timestamp": "2026-08-25T15:47:00Z",
"error_message": "User-reported live crash: xce_scheduler SIGABRT via glibc malloc_printerr (heap corruption detected during a malloc/free bookkeeping check -- 'double free or corruption'-class abort, not a clean segfault). Core captured from a live 3-node HA deployment run (--peers ctrl-1/ctrl-2/ctrl-3, -vvv). Backtrace: malloc_printerr -> kill_limit (src/lib/xcelimit.c:181) <- limit_update_config (src/scheduler/src/plugins/limit.c:76) <- plugin_config_update (src/scheduler/src/plugin.c:246) <- sched_init_config (src/scheduler/src/scheduler.c:936) <- scheduler_req_handler (src/scheduler/src/handler.c:687) <- vtask_entry (src/lib/xcectx.c:172) <- run_task/vcpu_entry (src/lib/vtaskmgr.c). limit_update_config's own locals at the crash frame: rc=-17 (-EEXIST), nlimits=7, i=0 -- crashes on (or near) the FIRST limit in a 7-limit config update.",
"file": "src/lib/xcelimit.c",
"root_cause": "Not yet root-caused. kill_limit() (xcelimit.c:181) is called from limit_update_config() (limit.c:76) during a live config update/reload (sched_init_config -> plugin_config_update fan-out) while nlimits=7 limits are being processed and rc=-17 (-EEXIST) is already set in the caller's frame -- suggests kill_limit is being called on a limit object that's already been freed or is being double-freed as part of an add-conflicts-with-existing (-EEXIST) error-handling/cleanup path in limit_update_config's loop over the new config's limits vs the existing limit table. Needs source read of limit_update_config()'s loop body and kill_limit()'s own free logic to confirm whether this is a double-free, a use-after-free, or a heap metadata corruption from an earlier out-of-bounds write that only surfaces later at this free call.",
"fix": "Not yet fixed -- investigating.",
"tags": [
"scheduler",
"limit-plugin",
"heap-corruption",
"crash",
"sigabrt",
"live-deployment"
],
"related_bugs": [],
"occurrences": 1,
"last_seen": "2026-08-25T15:47:00Z"
}
]
}