2016-05-04 52 views
1

我正在使用基于SWIG示例的PJSIP for android构建SIP Softphone。启用登录PJSIP for Android部队关闭应用程序

启用日志作为样本中描述:

LogConfig log_cfg = epConfig.getLogConfig(); 
SipLogWriter logWriter = new SipLogWriter(); 
log_cfg.setWriter(logWriter); 
log_cfg.setDecor(log_cfg.getDecor() & ~(pj_log_decoration.PJ_LOG_HAS_CR.swigValue() | pj_log_decoration.PJ_LOG_HAS_NEWLINE.swigValue())); 

在我的SipLogWriter类:

public class SipLogWriter extends LogWriter { 
    @Override 
    public void write(LogEntry entry) { 
     Log.d(Global.TAG, "[SipLogWriter] " + entry.getMsg()); 
    } 
} 

PJSIP LIB现在,然后暂停每本回溯:

05-04 10:32:10.534 I/DEBUG ( 281): backtrace: 
05-04 10:32:10.534 I/DEBUG ( 281):  #00 pc 00037b58 /system/lib/libc.so (tgkill+12) 
05-04 10:32:10.544 I/DEBUG ( 281):  #01 pc 00013fc9 /system/lib/libc.so (pthread_kill+52) 
05-04 10:32:10.544 I/DEBUG ( 281):  #02 pc 00014be7 /system/lib/libc.so (raise+10) 
05-04 10:32:10.544 I/DEBUG ( 281):  #03 pc 00011529 /system/lib/libc.so (__libc_android_abort+36) 
05-04 10:32:10.544 I/DEBUG ( 281):  #04 pc 0000fcb4 /system/lib/libc.so (abort+4) 
05-04 10:32:10.544 I/DEBUG ( 281):  #05 pc 00001259 /system/lib/libstdc++.so 
05-04 10:32:10.544 I/DEBUG ( 281):  #06 pc 00000afb /system/lib/libstdc++.so (__cxa_pure_virtual+6) 
05-04 10:32:10.544 I/DEBUG ( 281):  #07 pc 0015d4e8 /data/app/com.sample.app-1/lib/arm/libpjsua2.so (pj::Endpoint::utilLogWrite(pj::LogEntry&)+180) 
05-04 10:32:10.544 I/DEBUG ( 281):  #08 pc 0015d734 /data/app/com.sample.app-1/lib/arm/libpjsua2.so (pj::Endpoint::logFunc(int, char const*, int)+292) 
05-04 10:32:10.544 I/DEBUG ( 281):  #09 pc 001a9fe0 /data/app/com.sample.app-1/lib/arm/libpjsua2.so (log_writer+164) 
05-04 10:32:10.544 I/DEBUG ( 281):  #10 pc 0034420c /data/app/com.sample.app-1/lib/arm/libpjsua2.so (pj_log+2324) 
05-04 10:32:10.544 I/DEBUG ( 281):  #11 pc 0034436c /data/app/com.sample.app-1/lib/arm/libpjsua2.so (pj_log_4+44) 
05-04 10:32:10.544 I/DEBUG ( 281):  #12 pc 0025c9c4 /data/app/com.sample.app-1/lib/arm/libpjsua2.so (play_cb+568) 
05-04 10:32:10.544 I/DEBUG ( 281):  #13 pc 0029c454 /data/app/com.sample.app-1/lib/arm/libpjsua2.so (bqPlayerCallback+420) 
05-04 10:32:10.544 I/DEBUG ( 281):  #14 pc 00008daf /system/lib/libwilhelm.so 
05-04 10:32:10.544 I/DEBUG ( 281):  #15 pc 000559fd /system/lib/libmedia.so (android::AudioTrack::processAudioBuffer()+1156) 
05-04 10:32:10.544 I/DEBUG ( 281):  #16 pc 00055c69 /system/lib/libmedia.so (android::AudioTrack::AudioTrackThread::threadLoop()+168) 
05-04 10:32:10.544 I/DEBUG ( 281):  #17 pc 0000ef55 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+112) 
05-04 10:32:10.544 I/DEBUG ( 281):  #18 pc 0000eac5 /system/lib/libutils.so 
05-04 10:32:10.544 I/DEBUG ( 281):  #19 pc 000137b3 /system/lib/libc.so (__pthread_start(void*)+30) 
05-04 10:32:10.544 I/DEBUG ( 281):  #20 pc 00011893 /system/lib/libc.so (__start_thread+6) 

我怀疑它试图从错误的线程写入日志,但我不知道如何解决它。禁用LogWriter应用程序不会抛出此错误。

任何帮助表示赞赏。

+0

同样的问题。但在我的情况下,我需要日志,当我关闭 - 一切正常。当我启用日志,经过一段时间的应用程序下降与崩溃该日志试图从死线程或空对象做一些事情! – GensaGames

回答

0

我有同样的问题。我不知道现在是不是真的,但我解决了,如Official Doc。凡发现它是垃圾收集问题:

class MyApp { 
    private MyLogWriter logWriter; 

    public void init() 
    { 
     /* Maintain reference to log writer to avoid premature cleanup by GC */ 
     logWriter = new MyLogWriter(); 
     epConfig.getLogConfig.setWriter(logWriter); 
    } 
} 
0

正如GensaGames说,你需要保持一个参考,否则它会崩溃时,GC将决定清理对象。如果您使用依赖注入器(例如:dagger 2),则可以将自定义日志记录类添加到您的图依赖项,并将范围设置为Singleton或您的Application范围。

相关问题