[jitsi-users] Jitsi crashes when using camera


#1

Jitsi Version: Any (tried 3584, 3820, 3885 and latest 3909 both 64b and 32b)
WebCam: Logitech C250 & Logitech C910 (Jitsi doesn't even recognize HP Webcam HD-3110)
OS: Windows XP 64b SP2

When using video in any way Jitsi crashes with no system log entry.
This includes changing video options and any video chats.

I am not really sure where to go from here.
I have tried everything I can think of, but since there is no crash log (or log of any kind) I have nothing to go on

Any help would be greatly appreciated.

···

--
Brian Peyatt
Systems Engineer
ScanlineVFX/Los Angeles
Work: 310-827-1555


#2

When using video in any way Jitsi crashes with no system log entry.

Does "no system log entry" above mean/include Event Viewer?

This includes changing video options and any video chats.

Jitsi crashes when you open the Tools > Options dialog as soon as you
(try to) navigate to the Video tab?

I am not really sure where to go from here.
I have tried everything I can think of, but since there is no crash log (or
log of any kind) I have nothing to go on

Do you mean there are no Jitsi logs either?

Besides Event Viewer, the Java Virtual Machine creates hs_err_pid*.log
files at times after a crash either in the folder where Jitsi is
installed or in the %TEMP% folder.

Please use the build-in Jitsi log archiving as described at
http://jitsi.org/index.php/Documentation/FAQ#logs (it will also
include any Jitsi-related hs_err_pid*.log files) and send us the
resulting zip.

···

2012/2/17 Brian Peyatt <brian.peyatt@scanlinevfx.com>:


#3

When using video in any way Jitsi crashes with no system log entry.

Does "no system log entry" above mean/include Event Viewer?

Correct, no Event Viewer log of any kind (in response to Jitsi)

This includes changing video options and any video chats.

Jitsi crashes when you open the Tools> Options dialog as soon as you
(try to) navigate to the Video tab?

It opens the Tools > Options> Video dialog, but when you close the dialog Jitsi crashes.
When you initiate a video call/chat it works as expected, but when ending the call Jitsi crashes.

I am not really sure where to go from here.
I have tried everything I can think of, but since there is no crash log (or
log of any kind) I have nothing to go on

Do you mean there are no Jitsi logs either?

Besides Event Viewer, the Java Virtual Machine creates hs_err_pid*.log
files at times after a crash either in the folder where Jitsi is
installed or in the %TEMP% folder.

Please use the build-in Jitsi log archiving as described at
http://jitsi.org/index.php/Documentation/FAQ#logs (it will also
include any Jitsi-related hs_err_pid*.log files) and send us the
resulting zip.

I was unaware of jitsi specific logs. I will check them out and send info back. Thank you very much for your help.

···

On 2/17/2012 11:12 AM, Lyubomir Marinov wrote:

2012/2/17 Brian Peyatt<brian.peyatt@scanlinevfx.com>:

--
Brian Peyatt
Systems Engineer
ScanlineVFX/Los Angeles
Work: 310-827-1555


#4

Sending logs as requested

jitsi_log.zip (164 KB)

···

On 2/17/2012 11:12 AM, Lyubomir Marinov wrote:

2012/2/17 Brian Peyatt<brian.peyatt@scanlinevfx.com>:

When using video in any way Jitsi crashes with no system log entry.

Does "no system log entry" above mean/include Event Viewer?

This includes changing video options and any video chats.

Jitsi crashes when you open the Tools> Options dialog as soon as you
(try to) navigate to the Video tab?

I am not really sure where to go from here.
I have tried everything I can think of, but since there is no crash log (or
log of any kind) I have nothing to go on

Do you mean there are no Jitsi logs either?

Besides Event Viewer, the Java Virtual Machine creates hs_err_pid*.log
files at times after a crash either in the folder where Jitsi is
installed or in the %TEMP% folder.

Please use the build-in Jitsi log archiving as described at
http://jitsi.org/index.php/Documentation/FAQ#logs (it will also
include any Jitsi-related hs_err_pid*.log files) and send us the
resulting zip.

--
Brian Peyatt
Systems Engineer
ScanlineVFX/Los Angeles
Work: 310-827-1555


#5

Seb, do you think you will be able to look into this problem? It's
obviously in the DirectShow DataSource#stop() but I'm not sure what
else you need in order to fully understand and resolve it.


#6

Hi,

Without the hs_err_pidXXX file, it is hard to tell the cause of the crash.

Regards,

···

--
Seb

2012/2/18 Lyubomir Marinov <lubo@jitsi.org>

Seb, do you think you will be able to look into this problem? It's
obviously in the DirectShow DataSource#stop() but I'm not sure what
else you need in order to fully understand and resolve it.


#7

Found them. Thank you for your help, I really appreciate it.

hs_err_pidXXXX_lapro1044.zip (37.3 KB)

···

On 2/18/2012 4:14 AM, Sebastien Vincent wrote:

Hi,

Without the hs_err_pidXXX file, it is hard to tell the cause of the crash.

Regards,
--
Seb

2012/2/18 Lyubomir Marinov <lubo@jitsi.org <mailto:lubo@jitsi.org>>

    Seb, do you think you will be able to look into this problem? It's
    obviously in the DirectShow DataSource#stop() but I'm not sure what
    else you need in order to fully understand and resolve it.

--
Brian Peyatt
Systems Engineer
ScanlineVFX/Los Angeles
Work: 310-827-1555


#8

Bump.
Just curious if anybody has more info now that I have supplied more logs?

···

On 2/21/2012 6:56 AM, Brian Peyatt wrote:

Found them. Thank you for your help, I really appreciate it.

On 2/18/2012 4:14 AM, Sebastien Vincent wrote:

Hi,

Without the hs_err_pidXXX file, it is hard to tell the cause of the crash.

Regards,
--
Seb

2012/2/18 Lyubomir Marinov <lubo@jitsi.org <mailto:lubo@jitsi.org>>

    Seb, do you think you will be able to look into this problem? It's
    obviously in the DirectShow DataSource#stop() but I'm not sure what
    else you need in order to fully understand and resolve it.

--
Brian Peyatt
Systems Engineer
ScanlineVFX/Los Angeles
Work: 310-827-1555

--
Brian Peyatt
Systems Engineer
ScanlineVFX/Los Angeles
Work: 310-827-1555