New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pcrf crash with malloc(): invalid size (unsorted)
#1313
Comments
Could you send me a gdb log as below? $ gdb ./install/bin/open5gs-pcrfd
gdb> run
..(Aborted)
gdb> bt full Thanks a lot! |
Hi @acetcom and @WingPig99 I got the same error here as well. So, when go back and checked the commits,
It was output even if it goes back to the above commit. Before that,
In the above version this error was not occurred. |
This was fine with the old memory pool, but this is what happened when I changed the talloc. Can you run gdb ./install/bin/open5gs-pcrfd and get the 'bt full' log? Thanks a lot! |
@acetcom Yes, sure thing. Following is the log.
|
Hi @WingPig99 I don't know why talloc caused this problem. I would like to simulate the above scenario. Could you share the related pcap? I need a s1ap and diameter protocol. Thanks a lot! |
Hi @acetcom I got this error when I updated Open5GS for the first time this year and used herlesupreeth/docker_open5gs. I don't know if it's useful because it's a case where PCRF doesn't crash, but there are a few log files here. herlesupreeth/docker_open5gs#58 For your reference. |
Hi @acetcom I got log with the following version of which PCRF crashes.
My environment is as follows.
In addition, I set the static routing of eNodeB(Baicells) as follows.
Phone1)
Smartphone is the following model.
For each NF of Open5GS in Docker Host, the IP addresses described in
The time range of the log is
You can easily see the For your reference. |
Ho @WingPig99 and @s5uishida I've fixed the bug and updated the modification to the issues1313 branch. Let me know if you get the test results. Thanks a lot! |
Hi @s5uishida You reported the situation so well that I was able to fix this bug. Thank you very much. |
You're right. I've changed the log level from ERROR to WARN. Thanks a lot! |
Thank you for your quick fix. |
Hi, following is the crash log. Could you please give me some idea?
The text was updated successfully, but these errors were encountered: