Uh oh!
There was an error while loading. Please reload this page.
[Fix](core) Fix wal mgr heap use after free when stop doris - #33131
Conversation
doris-robot
commented
Apr 1, 2024
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
Yukang-Lian
commented
Apr 1, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Apr 1, 2024
TPC-H: Total hot run time: 38934 ms |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Uh oh!
There was an error while loading. Please reload this page.
Yukang-Lian
commented
Apr 2, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Apr 2, 2024
TPC-H: Total hot run time: 39193 ms |
doris-robot
commented
Apr 2, 2024
TPC-DS: Total hot run time: 181459 ms |
doris-robot
commented
Apr 2, 2024
ClickBench: Total hot run time: 30.16 s |
doris-robot
commented
Apr 2, 2024
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
da2877e to
ca8109bCompareYukang-Lian
commented
Apr 4, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Apr 4, 2024
TeamCity be ut coverage result: |
doris-robot
commented
Apr 4, 2024
TPC-H: Total hot run time: 38350 ms |
doris-robot
commented
Apr 4, 2024
TPC-DS: Total hot run time: 181579 ms |
doris-robot
commented
Apr 4, 2024
ClickBench: Total hot run time: 29.69 s |
doris-robot
commented
Apr 4, 2024
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
Yukang-Lian
commented
Apr 4, 2024
run p0 |
Yukang-Lian
commented
Apr 5, 2024
run buildall |
doris-robot
commented
Apr 5, 2024
TeamCity be ut coverage result: |
7c0e15f to
d9946a8CompareYukang-Lian
commented
Aug 13, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Aug 13, 2024
TPC-H: Total hot run time: 39722 ms |
doris-robot
commented
Aug 13, 2024
TPC-DS: Total hot run time: 190245 ms |
doris-robot
commented
Aug 13, 2024
ClickBench: Total hot run time: 31.18 s |
Yukang-Lian
commented
Aug 13, 2024
run buildall |
doris-robot
commented
Aug 13, 2024
TPC-H: Total hot run time: 39610 ms |
doris-robot
commented
Aug 13, 2024
TPC-DS: Total hot run time: 186658 ms |
doris-robot
commented
Aug 13, 2024
ClickBench: Total hot run time: 32.13 s |
Yukang-Lian
commented
Aug 14, 2024
run cloud_p0 |
PR approved by at least one committer and no changes requested. |
Problem: When the process stops, there is a heap use after free error with the WAL manager. Reason: During the startup process, if the storage engine does not initialize successfully and the main program directly returns 0, the WAL manager, which was created during initialization and started a thread to periodically check disk space, will encounter an issue. When the program exits and returns 0, local variables are destroyed first before the thread is properly terminated. If the thread attempts to access those local variables at this point, it leads to a heap use after free error. Solution: Ensure that the thread for periodically checking disk space is only started after the storage engine has been successfully initialized. ## Proposed changes Issue Number: close #xxx <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
…3131) Problem: When the process stops, there is a heap use after free error with the WAL manager. Reason: During the startup process, if the storage engine does not initialize successfully and the main program directly returns 0, the WAL manager, which was created during initialization and started a thread to periodically check disk space, will encounter an issue. When the program exits and returns 0, local variables are destroyed first before the thread is properly terminated. If the thread attempts to access those local variables at this point, it leads to a heap use after free error. Solution: Ensure that the thread for periodically checking disk space is only started after the storage engine has been successfully initialized. ## Proposed changes Issue Number: close #xxx <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
…3131) Problem: When the process stops, there is a heap use after free error with the WAL manager. Reason: During the startup process, if the storage engine does not initialize successfully and the main program directly returns 0, the WAL manager, which was created during initialization and started a thread to periodically check disk space, will encounter an issue. When the program exits and returns 0, local variables are destroyed first before the thread is properly terminated. If the thread attempts to access those local variables at this point, it leads to a heap use after free error. Solution: Ensure that the thread for periodically checking disk space is only started after the storage engine has been successfully initialized. ## Proposed changes Issue Number: close #xxx <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [dev@doris.apache.org](mailto:dev@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc...
Problem: When the process stops, there is a heap use after free error with the WAL manager.
Reason: During the startup process, if the storage engine does not initialize successfully and the main program directly returns 0, the WAL manager, which was created during initialization and started a thread to periodically check disk space, will encounter an issue. When the program exits and returns 0, local variables are destroyed first before the thread is properly terminated. If the thread attempts to access those local variables at this point, it leads to a heap use after free error.
Solution: Ensure that the thread for periodically checking disk space is only started after the storage engine has been successfully initialized.
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...