[jitsi-users] jitsi crashes with out of memory errors taking the system to a collapse


#1

Hi everyone,

since i run jitsi with a SIP account, it get a lot of crashes with my
system.

8 GB RAM

One of these events looks like this in the logs:

Apr 28 13:59:59 eve gnome-session: 13:59:59.715 SCHWERWIEGEND: [7621]
service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged().190
An error occurred while executing RegistrationSta
teChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of
net.java.sip.communicator.impl.globaldisplaydetails.GlobalStatusServiceImpl@5818806d
Apr 28 13:59:59 eve gnome-session: java.lang.OutOfMemoryError: unable to
create new native thread
Apr 28 13:59:59 eve gnome-session: at java.lang.Thread.start0(Native Method)
Apr 28 13:59:59 eve gnome-session: at
java.lang.Thread.start(Thread.java:714)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.globaldisplaydetails.GlobalStatusServiceImpl.publishStatusInternal(GlobalStatusServiceImpl.java:335)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.globaldisplaydetails.GlobalStatusServiceImpl.handleProviderRegistered(GlobalStatusServiceImpl.java:731)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.globaldisplaydetails.GlobalStatusServiceImpl.registrationStateChanged(GlobalStatusServiceImpl.java:708)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:176)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.setRegistrationState(SipRegistrarConnection.java:724)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.setRegistrationState(SipRegistrarConnection.java:700)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processOK(SipRegistrarConnection.java:491)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:906)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:737)
Apr 28 13:59:59 eve gnome-session: at
net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:751)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:296)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:196)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1480)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.stack.SIPClientTransaction.nonInviteClientTransaction(SIPClientTransaction.java:643)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:550)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:1554)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:583)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:492)
Apr 28 13:59:59 eve gnome-session: at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
Apr 28 13:59:59 eve gnome-session: at java.lang.Thread.run(Thread.java:745)
Apr 28 14:00:03 eve gnome-session: ** (gedit:9817): CRITICAL **:
document_saved: assertion 'error->domain == G_CONVERT_ERROR ||
error->domain == G_IO_ERROR' failed
Apr 28 14:00:05 eve kernel: [13476.703044] traps: gsettings[17222] trap
int3 ip:3b6fe504e9 sp:7ffd6e2d55c0 error:0
Apr 28 14:00:05 eve kernel: traps: gsettings[17222] trap int3
ip:3b6fe504e9 sp:7ffd6e2d55c0 error:0
Apr 28 14:00:05 eve abrt-hook-ccpp: Saved core dump of pid 17222
(/usr/bin/gsettings) to /var/tmp/abrt/ccpp-2015-04-28-14:00:05-17222
(9580544 bytes)

-- best regards, Marius


#2

It got confirmed: without the SIP account enabled, the system is running
smoothly and without crashes,
with jitsi running from the beginning. Conclusion: The problem must
beinside the SIP code.

I shall note, that i saw a lot of SIP online -> offline -> online ->
offline for that account when it was enabled.

best regards,
Marius

ยทยทยท

Am 29.04.2015 um 21:22 schrieb Marius:

Hi everyone,

since i run jitsi with a SIP account, it get a lot of crashes with my
system.

8 GB RAM