[jitsi-dev] crash during voice call


#1

This was a conversation between two jitsi clients (one Windows XP, the
other Ubuntu 12.04) with voice. A few seconds after ZRTP was
negotiated, and before any voice managed to get across, my client (on
Ubuntu) crashed. The Windows client appeared to think the call was
still going on.

This log is from the Ubuntu Jitsi installation that crashed: v.1.1.4388.10227

Cheers

Alex

jitsi_crash_edited.log.gz (5.99 KB)


#2

This was a conversation between two jitsi clients (one Windows XP, the
other Ubuntu 12.04) with voice. A few seconds after ZRTP was
negotiated, and before any voice managed to get across, my client (on
Ubuntu) crashed.

Do you mean that the Jitsi/java process died?

<jitsi_crash_edited.log.gz>

The log does not contain information about the cause of the death of the Jitsi/java process. We will need the dump printed out by the Java VM at the time of death. It might be in a file in the ~/.jitsi or ~/.sip-communicator directory, in your home directory or in the temporary directory of your operating system. If Jitsi is started in a terminal, it will likely print a message related to that file upon a crash.

···

On 06.01.2013, at 20:07, ix4svs@gmail.com wrote:


#3

This was a conversation between two jitsi clients (one Windows XP,
the other Ubuntu 12.04) with voice. A few seconds after ZRTP was
negotiated, and before any voice managed to get across, my client
(on Ubuntu) crashed.

Do you mean that the Jitsi/java process died?

I mean that all Jitsi windows disappeared.

<jitsi_crash_edited.log.gz>

The log does not contain information about the cause of the death of
the Jitsi/java process. We will need the dump printed out by the Java
VM at the time of death. It might be in a file in the ~/.jitsi or
~/.sip-communicator directory, in your home directory or in the
temporary directory of your operating system. If Jitsi is started in
a terminal, it will likely print a message related to that file upon
a crash.

These are the files in my .jitsi directory. The snippet I sent was from
log/jitsi0.log.0 (the most recent log file), with large chunks of what
seemed as redundant text removed (I'm also not comfortable sending all
my contact information to a mailing list, as that's included in the log).

Which of the files below would be useful?

alex@blackbook:~/.jitsi$ ls -la
total 856
drwxrwxr-x 8 alex alex 4096 Jan 6 18:06 .
drwx------ 52 alex alex 16384 Jan 6 17:33 ..
drwxrwxr-x 15 alex alex 4096 Sep 28 07:43 avatarcache
-rw-rw-r-- 1 alex alex 141586 Jan 6 18:05 contactlist.xml
-rw-rw-r-- 1 alex alex 7838 Jan 6 18:04 .fmj.registry
-rw-rw-r-- 1 alex alex 1280 Jan 6 16:13 GNUZRTP4J.zid
drwxrwxr-x 5 alex alex 4096 May 19 2012 history_ver1.0
drwxrwxr-x 2 alex alex 4096 Sep 26 21:44 keybindings
drwxrwxr-x 2 alex alex 4096 Jan 6 18:06 log
drwxrwxr-x 122 alex alex 20480 Oct 21 01:23 sip-communicator.bin
-rw-rw-r-- 1 alex alex 623226 Jan 6 18:06 sip-communicator.properties
drwxrwxr-x 2 alex alex 4096 Sep 26 21:44 spellingDictionaries
alex@blackbook:~/.jitsi$ ls -la log/
total 3256
drwxrwxr-x 2 alex alex 4096 Jan 6 18:06 .
drwxrwxr-x 8 alex alex 4096 Jan 6 18:06 ..
-rw-rw-r-- 1 alex alex 18371 Jan 6 18:05 jitsi0.log.0
-rw-rw-r-- 1 alex alex 121226 Jan 6 16:14 jitsi0.log.1
-rw-rw-r-- 1 alex alex 22532 Jan 3 10:07 jitsi0.log.2
-rw-rw-r-- 1 alex alex 186155 Aug 29 23:10 jitsi0.pcap
-rw-rw-r-- 1 alex alex 2829543 Aug 29 22:35 jitsi1.pcap
-rw-rw-r-- 1 alex alex 89152 Aug 29 16:25 jitsi2.pcap
alex@blackbook:~/.jitsi$

Cheers

Alex

···

On 06/01/13 19:02, Lyubomir Marinov wrote:

On 06.01.2013, at 20:07, ix4svs@gmail.com wrote:


#4

We need a file with a name in the form hs_err_pid<pid>.log. Here's a snippet from Sun/Oracle's documentation on the subject:

When a fatal error occurs an error log is created in the file hs_err_pid<pid>.log (where <pid> is the process id of the process). Where possible the file is created in the working directory of the process. In the event that the file cannot be created in the working directory (insufficient space, permission problem, or other issue) then the file is created in the temporary directory for the operating system. On Solaris and Linux the temporary directory is /tmp. On Windows the temporary directory is specified by the value of the TMP environment variable, or if that is not defined, the value of the TEMP environment variable.

···

On 06.01.2013, at 22:07, Alexandros Papadopoulos <ap@member.fsf.org> wrote:

<jitsi_crash_edited.log.gz>

The log does not contain information about the cause of the death of
the Jitsi/java process. We will need the dump printed out by the Java
VM at the time of death. It might be in a file in the ~/.jitsi or
~/.sip-communicator directory, in your home directory or in the
temporary directory of your operating system. If Jitsi is started in
a terminal, it will likely print a message related to that file upon
a crash.

These are the files in my .jitsi directory. The snippet I sent was from
log/jitsi0.log.0 (the most recent log file), with large chunks of what
seemed as redundant text removed (I'm also not comfortable sending all
my contact information to a mailing list, as that's included in the log).

Which of the files below would be useful?


#5

<snip>

Unfortunately such a file doesn't appear to exist on my system - I looked in /tmp and ~/.jitsi with find and locate and there is nothing matching hs_err_pid*

Anything else that can be done to troubleshoot this?

Alex

···

On 06/01/13 21:04, Lyubomir Marinov wrote:

On 06.01.2013, at 22:07, Alexandros Papadopoulos <ap@member.fsf.org> > wrote:

<jitsi_crash_edited.log.gz>

The log does not contain information about the cause of the death
of the Jitsi/java process. We will need the dump printed out by
the Java VM at the time of death. It might be in a file in the
~/.jitsi or ~/.sip-communicator directory, in your home directory
or in the temporary directory of your operating system. If Jitsi
is started in a terminal, it will likely print a message related
to that file upon a crash.

These are the files in my .jitsi directory. The snippet I sent was
from log/jitsi0.log.0 (the most recent log file), with large chunks
of what seemed as redundant text removed (I'm also not comfortable
sending all my contact information to a mailing list, as that's
included in the log).

Which of the files below would be useful?

We need a file with a name in the form hs_err_pid<pid>.log. Here's a
snippet from Sun/Oracle's documentation on the subject:


#6

Can also be found in the java installation dirs (bin, etc.).
Do a search there. Sometimes it is also written to the base directory
of the running java application (the "." of the system class path).

Best regards,
Matt

···

Am 11.01.2013 14:34, schrieb Alexandros Papadopoulos:

On 06/01/13 21:04, Lyubomir Marinov wrote:

On 06.01.2013, at 22:07, Alexandros Papadopoulos <ap@member.fsf.org> >> wrote:

<jitsi_crash_edited.log.gz>

The log does not contain information about the cause of the death
of the Jitsi/java process. We will need the dump printed out by
the Java VM at the time of death. It might be in a file in the
~/.jitsi or ~/.sip-communicator directory, in your home directory
or in the temporary directory of your operating system. If Jitsi
is started in a terminal, it will likely print a message related
to that file upon a crash.

These are the files in my .jitsi directory. The snippet I sent was
from log/jitsi0.log.0 (the most recent log file), with large chunks
of what seemed as redundant text removed (I'm also not comfortable
sending all my contact information to a mailing list, as that's
included in the log).

Which of the files below would be useful?

We need a file with a name in the form hs_err_pid<pid>.log. Here's a
snippet from Sun/Oracle's documentation on the subject:

<snip>

Unfortunately such a file doesn't appear to exist on my system - I
looked in /tmp and ~/.jitsi with find and locate and there is nothing
matching hs_err_pid*

Anything else that can be done to troubleshoot this?

Alex


#7

Can also be found in the java installation dirs (bin, etc.).
Do a search there. Sometimes it is also written to the base directory
of the running java application (the "." of the system class path).

Sorry but even a find / -name hs_err_pid*.log did not uncover anything.

Alex

···

On 11/01/13 13:54, Buddy Butterfly wrote:

Am 11.01.2013 14:34, schrieb Alexandros Papadopoulos:

On 06/01/13 21:04, Lyubomir Marinov wrote:

On 06.01.2013, at 22:07, Alexandros Papadopoulos <ap@member.fsf.org> >>> wrote:

<jitsi_crash_edited.log.gz>

The log does not contain information about the cause of the death
of the Jitsi/java process. We will need the dump printed out by
the Java VM at the time of death. It might be in a file in the
~/.jitsi or ~/.sip-communicator directory, in your home directory
or in the temporary directory of your operating system. If Jitsi
is started in a terminal, it will likely print a message related
to that file upon a crash.

These are the files in my .jitsi directory. The snippet I sent was
from log/jitsi0.log.0 (the most recent log file), with large chunks
of what seemed as redundant text removed (I'm also not comfortable
sending all my contact information to a mailing list, as that's
included in the log).

Which of the files below would be useful?

We need a file with a name in the form hs_err_pid<pid>.log. Here's a
snippet from Sun/Oracle's documentation on the subject:

<snip>

Unfortunately such a file doesn't appear to exist on my system - I
looked in /tmp and ~/.jitsi with find and locate and there is nothing
matching hs_err_pid*

Anything else that can be done to troubleshoot this?

Alex

--
Know anyone who needs personal help with their computer?
http://ukcomputerhelp.net