aarch64 的CentOS Linux release 7.6.1810 (AltArch),brpc1.5.0 echo_test 退出报错sched_to itself!double free or corruption

Open
#3,231 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

Reproduce the failure with echo_server on CentOS Linux 7.6.1810 (AltArch), brpc 1.5.0, and protobuf 2.5.0, then inspect src/bthread/task_group.cpp around line 629 and the shutdown path reported by the log. Done means stopping the server with Ctrl+C exits cleanly without “sched_to itself!” or double-free errors.

Written by the indexing model from the issue text.

Description

Describe the bug
1、启动echo_server ,啥都不做
sudo ./echo_server --port=8341
I0226 18:12:36.422261 64782 src/brpc/server.cpp:1113] Server[EchoServiceImpl] is serving on port=8341.
I0226 18:12:36.422582 64782 src/brpc/server.cpp:1116] Check out http://tjyxy01-ks3-dev144059169.tjyxy01.ksyun.com:8341 in web browser.
EchoServer started at 0.0.0.0:8341
2、ctrl+c退出即报错
I0226 18:12:37.075939 64782 src/brpc/server.cpp:1173] Server[EchoServiceImpl] is going to quit
F0226 18:12:37.076134 64821 src/bthread/task_group.cpp:629] bthread=4294975488 sched_to itself!
*** Error in `./echo_server': double free or corruption (!prev): 0x0000ffff1401c780 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7d1ec)[0xffffb47fd1ec]
/lib64/libstdc++.so.6(_ZNSs7reserveEm+0xb0)[0xffffb4acda74]
./echo_server[0x57a5a0]
./echo_server[0x4ab4e8]

To Reproduce

Expected behavior
正常退出不要报错

Versions
OS:CentOS Linux release 7.6.1810 (AltArch),
Compiler:
brpc:1.5.0
protobuf:2.5.0

Additional context/screenshots

Dominant language
C++
Stars
17.6k
Forks
4.2k
Avg merge
3d 17h
Merged PRs (30d)
72

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/brpc

All issues in apache/brpc

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.