Open GoogleCodeExporter opened 9 years ago
I see this on the Flipout as well. To be more precise, shortly after each
successful call, the entire Android user interface crashes and restarts
(blinking MotoBlur logo).
Maybe sipdroid has a resource leak that depletes some critical resource (such
as memory)?
Original comment by michael....@gmail.com
on 18 Jan 2012 at 1:29
(PS.: Using Sipdroid 2.4 beta.)
Original comment by michael....@gmail.com
on 18 Jan 2012 at 1:31
Interestingly, the same problem occurs with CSipSimple (see
http://code.google.com/p/csipsimple/issues/detail?id=1539). Do the two
projects share a common component (library, SIP stack, ...)?
Original comment by michael....@gmail.com
on 26 Jan 2012 at 7:45
I have developed a API that uses android.media.AudioRecord that suffers a bad
behavior on read() after a second start record sequence:
// first time, works fine
audio = new AudioRecord(...)
audio.startRecording();
audio.read(buff, off, size);
audio.stop();
audio.release();
audio=null;
// second try, bad behavior
audio = new AudioRecord(...)
audio.startRecording();
audio.read(buff, off, size); // the internal native call to
AudioRecord.native_read_in_short_array() seems to return but it's very, very
slow. Just happens on MB511.
audio.stop();
audio.release();
audio=null;
...
I tried to reuse the object (without calling release()) but it seems to give a
single extra recorder. The third one fails too.
I guess this is a problem on native code implementation.
Hope this helps someone else having issues with this device.
Original comment by gilson...@gmail.com
on 15 Jun 2012 at 5:25
Original issue reported on code.google.com by
fmgu...@gmail.com
on 4 Oct 2010 at 10:23