[Home]

Summary:ASTERISK-28407: Segfault in hash_ao2_find_next at astobj2_hash.c:581
Reporter:Ross Beer (rossbeer)Labels:
Date Opened:2019-05-07 07:31:11Date Closed:2021-03-30 07:47:28
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/PBX
Versions:13.26.0 GIT Frequency of
Occurrence		Occasional
Related
Issues:
Environment:CentOS 7Attachments:( 0) core.asterisk.152013.1557226127-thread1.txt
Description:Segfault while finding ao2 object at astobj2_hash.c:581

{noformat}
#0  0x0000000000461311 in hash_ao2_find_next (self=0x7f32394f5108, state=0x7f32fa082780, prev=0x7f323a0b1180) at astobj2_hash.c:581
       node = 0xffffffff
       arg = 0x0
       flags = 7
       bucket_cur = 39
       cmp = 0
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2019-05-07 07:31:12.857-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: George Joseph (gjoseph) 2019-06-04 14:16:01.807-0500

Any more occurrences of this crash?  At the time, it looks like there were a bunch of threads waiting on a system memory allocation lock in libc.

I'm still nosing around.

...and you wouldn't happen to still have the binaries that would go with that coredump would you?

By: Ross Beer (rossbeer) 2019-06-04 14:47:08.207-0500

Sadly I don't have the binaries any more, I have updated to a later GIT version. I haven't had a reoccurrence of this issue since.

There are other issues with astobj2 open though: ASTERISK-28434 and ASTERISK-28434 I have binaries for 28434