[asterisk-users] Asterisk 12 - zombie processes

[Yaron Nachum]

Hello Mathew and everyone,
We had another crash on the 12.6.1 machine. This time it was Sigmentation
Fault. I opened another issue - ASTERISK-24493
<https://issues.asterisk.org/jira/browse/ASTERISK-24493>.

Yaron.

On Tue, Nov 4, 2014 at 6:16 PM, Yaron Nachum <nachum.yaron at gmail.com> wrote:

> Mathew,
> We are aware that this is an open source product, and our expectations are
> clear.
> All we are asking is that once there is someone assigned to the issue, he
> will guide us in what other data or tests should be performed in order to
> diagnose and fix the issue in the shortest time.
>
> Sorry if the message is not understood.
> Yaron
>
> On Tue, Nov 4, 2014 at 3:59 PM, Matthew Jordan <mjordan at digium.com> wrote:
>
>> On Tue, Nov 4, 2014 at 12:59 AM, Yaron Nachum <nachum.yaron at gmail.com>
>> wrote:
>> > Hello Asterisk users & developers,
>> > I have opened an issue few days ago regarding the crash and the zombie
>> > processes. I haven't received any response and it has't been assigned.
>> > If something is wrong or missing with the issue please get back to me
>> and I
>> > will handle it.
>> >
>> > Please look into it because we still have crashes every day or two, and
>> we
>> > can't reproduce the issue in our lab with a simulator.
>> >
>>
>> To set expectations here:
>>
>> This is an open source project. No one is under any obligation to look
>> at your issue.
>>
>> There are currently around 20 issues or so in the issue tracker in
>> Triage. Bug marshals are working through those issues as fast as they
>> can, but generally they work from oldest to newest. If an older issue
>> takes a lot of investigation... well, there's only so many hours in a
>> day.
>>
>> Even after an issue is triaged, that is not a guarantee that someone
>> will fix your issue. It is a crash, and that generally means it is
>> higher priority - however, if you can't reproduce it in a lab
>> environment or provide instructions on how it is reproduced, then you
>> have to hope that a developer who does look at it can infer the cause
>> of the crash from the information available. Any information you can
>> provide beyond the backtrace on how to reproduce the issue will help a
>> developer who looks at it.
>>
>> Again, however, no one is under any obligation to fix the issue. If
>> you need more assurance that your issue is resolved, I'd highly
>> recommend looking at issuing a bug bounty [1], or contacting a
>> developer in the Asterisk Developer Community for assistance.
>>
>> [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties
>>
>> --
>> Matthew Jordan
>> Digium, Inc. | Engineering Manager
>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> Check us out at: http://digium.com & http://asterisk.org
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> New to Asterisk? Join us for a live introductory webinar every Thurs:
>>                http://www.asterisk.org/hello
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20141105/f48efca3/attachment.html>