-
Notifications
You must be signed in to change notification settings - Fork 571
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
OpenSIPS 1.10 segfault on fm_remove_free #126
Comments
Others have had success with e6f4a51. I did not. Program terminated with signal 11, Segmentation fault. |
Issue #83 reads similar to this. So, It has the memlog (1.3M) and the full backtrace. The first line could be telling: |
Hi Jeff, Thanks for your report- I noted the also your email. The log and backtrace confirm that the original fix done by Ovidiu has some side-effect (double free in some cases). I will do some digging to find out the problem. Regards, |
…ogether with the lumps). Reported by Jeff Pyle. Fixing bug #126
…ogether with the lumps). Reported by Jeff Pyle. Fixing bug #126
…ogether with the lumps). Reported by Jeff Pyle. Fixing bug #126
…ogether with the lumps). Reported by Jeff Pyle. Fixing bug #126
Jeff, please update from GIT - all supported version were fix. Confirmation on the fix will be appreciated. |
Bogdan, the fix prevents the crash. Yay! However, I see the following warning from modules/uac_auth/auth.c:
Memory use is stable for all the processes after a few dozen calls utilizing uac_auth(). False alarm? |
Reported by Jeff Pyle, part of fixing issue #126.
Reported by Jeff Pyle, part of fixing issue #126.
Reported by Jeff Pyle, part of fixing issue #126.
Reported by Jeff Pyle, part of fixing issue #126.
Warnings fixed also, thank you, closing this report. |
I've been having some stability problems with dcb87bc from Nov 8. It has crashed in a variety of ways (mostly down and hard), but all appear to have fm_remove_free in common. Two backtraces are below - telephone numbers changed to protect the guilty.
==> backtrace1.log
==> backtrace2.log
The text was updated successfully, but these errors were encountered: