# rad node start panics every few minutes
My Radicle node panics after a few minutes or less of runtime. It usually stays running long enough to perform a single action.
The panic seems to be caused by: radicle_protocol::wire::serialize:
“advance out of bounds: the len is 65526 but advancing by 65536”
Here is the backtrace:
2025-08-28T05:43:03.817-04:00 INFO wire Peer z6MkmkWUzDzS1RcRyxzo6zf5E3GQSjXUzUJA5cUc2tkjEUty fetched rad:zcq9LUE4byh8rBiB1st7aBnezPkU from us successfully The first line is the issue title. The issue
description follows, and must be separated by a blank line, just like a commit message. Markdown is supported in the title and description. --> 2025-08-28T05:43:04.974-04:00 INFO wire Peer
z6MkmkWUzDzS1RcRyxzo6zf5E3GQSjXUzUJA5cUc2tkjEUty fetched rad:z43JgdBzAPTmR1oXkQPm6Ah9GxFnq from us successfully 2025-08-28T05:43:05.554-04:00 WARN worker Read channel timed out for upload-pack
rad:zcq9LUE4byh8rBiB1st7aBnezPkU 2025-08-28T05:43:05.555-04:00 INFO wire Peer z6Mkf3h4S5akszuqqbmckmsSekbUgJEe1nmBxuRJP53bJAqe fetched rad:zcq9LUE4byh8rBiB1st7aBnezPkU from us successfully thread 'service'
panicked at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bytes-1.10.1/src/lib.rs:172:5: advance out of bounds: the len is 65526 but advancing by 65536 stack backtrace:
0: __rustc::rust_begin_unwind 1: core::panicking::panic_fmt 2: bytes::panic_advance 3: radicle_protocol::wire::serialize 4: <radicle_node::wire::Wire<D,S,G> as reactor::reactor::Handler>::handle_command
5: reactor::reactor::Runtime<H,P>::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. 2025-08-28T05:43:06.005-04:00 ERROR worker Error on upload-pack channel read for rad:zcq9LUE4byh8rBiB1st7aBnezPkU:
error reading from stream: channel is disconnected 2025-08-28T05:43:06.005-04:00 ERROR worker Error on upload-pack channel read for rad:zcq9LUE4byh8rBiB1st7aBnezPkU: error reading from stream: channel is
disconnected 2025-08-28T05:43:06.005-04:00 WARN worker Error reading stdout to upload-pack reporter: error writing to stream: channel is disconnected 2025-08-28T05:43:06.006-04:00 ERROR worker Unable to
report fetch result: worker channel disconnected 2025-08-28T05:43:06.006-04:00 ERROR worker Unable to report fetch result: worker channel disconnected thread 'main' panicked at
crates/radicle-node/src/runtime.rs:334:29: called `Result::unwrap()` on an `Err` value: Any { .. } stack backtrace:
0: __rustc::rust_begin_unwind 1: core::panicking::panic_fmt 2: core::result::unwrap_failed 3: radicle_node::runtime::Runtime::run
4: radicle_node::main
Any suggestions on where to begin patching the issue?
Thanks for the report. This is a known issue which sadly slipped into 1.3. A fix is already merged to master, see commit
Thus, to get this fix you can currently build on top of this commit, or on the release candidate for 1.4, which is tagged as
Otherwise please wait for 1.4 to be released next week. Thanks for your patience and offering to help.
Closing this now, since a fix for this was released with 1.3.1 and 1.4.0.