[jitsi-users] Jitsi Crashes on Video or Desktop Sharing (Windows Only)


#1

Hi

I've been trialing Jitsi recently between my Linux machines and
Windows machines. Most features work great, however when Windows users
initiate a call which uses video (video call or desktop share) then
Jitsi just crashes.

I have had one user report that their Window's install crashed when
receiving a desktop share call as well - though I haven't confirmed
this yet.

I have been able to reliably reproduce the issue with my Windows
machine, and the crash appears to happen in jnffmpeg.dll (which would
make sense due to the video nature).

i've included the hs_err_pid log file - this is just about my last
remaining hurdle to overcome, so any help in this matter would be most
appreciated.

I have just installed and tested 2.4.4997 and, at least on screen
sharing, it worked as expected. I will try and test with video a
little later.

Incidentally, whilst downloading older versions for test, I was told
that jitsi-2.2.4603.9615-x64.exe and jitsi-2.0-latest-x86.exe were
unsafe files (subsequent scans with virustotal.com showed they were
ok) but 2.4-latest.exe was ok. I guess this was a false-positive, but
any idea what might have tripped the filter?

cheers

hs_err_pid3024.log (37.7 KB)


#2

when Windows users
initiate a call which uses video (video call or desktop share) then
Jitsi just crashes.

Thank you for the feedback! We fixed the (video call and/or desktop
share) crash shortly AFTER releasing 2.6.

Incidentally, whilst downloading older versions for test, I was told
that jitsi-2.2.4603.9615-x64.exe and jitsi-2.0-latest-x86.exe were
unsafe files (subsequent scans with virustotal.com showed they were
ok) but 2.4-latest.exe was ok. I guess this was a false-positive, but
any idea what might have tripped the filter?

We had false positives before, we contacted as many anti-virus
software developers as possible to fix their definitions. Anyway, it's
quite possible we weren't signing our binaries back then.

ยทยทยท

2015-02-05 14:52 GMT+02:00 Robert Colvin <robert.r.colvin@gmail.com>: