[jitsi-users] Latest stable version crashes on both ends when trying to establish video call


#1

Hi folks,

                I just installed the latest stable build 2.6.5390 on both
Win 7 64 bit and Win 8.1 64 bit systems. Both systems are on the same local
network along with the Openfire server. Chat and voice calls work fine, but
when trying to establish a video call, whenever the receiver tries to answer
the call, Jitsi crashes on both systems immediately. I have checked the
logs and there is nothing in there to indicate why, in fact it appears that
the crashes happen in such a way that logging just stops completely at that
point. This happens regardless of which system is the call initiator.

                The previous stable build worked fine for all call types on
these systems. I can provide any logs and/or pcaps as necessary.

Thanks,

                Ken


#2

Hi Ken

I have just reported the exact same issue, my logs show that it is a
problem in jnfmpeg.dll

my report doesnt appear to have showed up in the mailing list yet -
here's a copy for you.

···

--------------------------------------------------------------------------------------------------------------------------------------------

"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!

On Thu, Feb 5, 2015 at 3:10 PM, Ken Ayotte <ken@kcayotte.net> wrote:

Hi folks,

                I just installed the latest stable build 2.6.5390 on both
Win 7 64 bit and Win 8.1 64 bit systems. Both systems are on the same local
network along with the Openfire server. Chat and voice calls work fine, but
when trying to establish a video call, whenever the receiver tries to answer
the call, Jitsi crashes on both systems immediately. I have checked the
logs and there is nothing in there to indicate why, in fact it appears that
the crashes happen in such a way that logging just stops completely at that
point. This happens regardless of which system is the call initiator.

                The previous stable build worked fine for all call types on
these systems. I can provide any logs and/or pcaps as necessary.

Thanks,

                Ken

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

I just installed the latest stable build 2.6.5390 on both Win
7 64 bit and Win 8.1 64 bit systems. Both systems are on the same local
network along with the Openfire server. Chat and voice calls work fine,

but

when trying to establish a video call, whenever the receiver tries to

answer

the call, Jitsi crashes on both systems immediately. I have checked the

logs

and there is nothing in there to indicate why, in fact it appears that the
crashes happen in such a way that logging just stops completely at that
point. This happens regardless of which system is the call initiator.

We're aware of it and working hard on a solution. We'll likely do a bugfix
release soon.

                The previous stable build worked fine for all call types

on

these systems. I can provide any logs and/or pcaps as necessary.

Thanks,

                Ken

Ingo


#4

Thank you very much for the feedback, guys! We believe we managed to
fixed the problem and committed a fix today. (As Ingo said, we'll
likely push a bugfix release soon.)