[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Protux-devel] MustuxAudioBus RFC answer
From: |
Remon Sijrier |
Subject: |
[Protux-devel] MustuxAudioBus RFC answer |
Date: |
Sat, 18 Oct 2003 16:28:51 +0200 |
User-agent: |
KMail/1.5.3 |
Hi Luciano,
//LG: but the buffers are only bzero'd, not destroyed. They are always valid
(as long the bus is open, ofcourse). They are invalid only when bus is
closed, but nobody is supposed to call geT_levels from a closed bus... (RFC)
Well, the reason may not be the right one, but it was craching on for this
reason:
(if((transferSize < 0) || (!transferBuffer)),
maybe the transferSize < 0 check is nonsense, but the other is for sure the
reason why protux had random segfaults!)
The only thing I can think of now, is that after a really long recording (then
it was crashing, not for short recordings) the audioBus is closed, but due
the high CPU usage (for building the peaks), the updateTimer for BusMonitor
isn't stopped within time. Then there can be a call to a nonexistent object.
Remon