On Sat, May 19, 2012 at 11:15:17PM +0300, Kai Vehmanen wrote:
> Hi,
>
> On Thu, 10 May 2012, S. Massy wrote:
>
> >It seems, however, that aadding many such ops in a short period of time
> >causes ecasound to segfault. Here is the backtrace:
>
> this looks a lot like something that could happen without the recent
> fix in git master (commit ca925a389154774ca7ff69d2f141f1c9000a2050 I
> pushed on Apr 17). Are you running the latest git?
Yes, this is reproductible with current (as of today) HEAD.
> But the problem is that this should be fixed in git already and the
> code looks correct. It could be some case is still missed, even with
> the latest code...
This does not occur if JACK output is not used. Could the JACK driver be
part of that sspecial case?
Cheers,
S.M.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Received on Sun May 20 04:15:04 2012
This archive was generated by hypermail 2.1.8 : Sun May 20 2012 - 04:15:04 EEST