[jitsi-users] Jitsi 2.2.4603.9615 for Windows crashes upon start


#1

Hello Group,

A friend of mine is using the the latest version of Jitsi (downloaded
today) and it simply will not start. Upon starting the program, he
immediately gets a window saying "ouch, Jitsi seems to have crashed" and
offers him to restart it. When he does, the same thing happens.

He's on Windows XP SP3. Anyone know what might be going on? Also, if a
crash report would help, I'd happy to attach it but I need to know where
Jitsi for Windows stores the report.

Thanks,
Anthony


#2

This sounds like an issue I had when I first installed Jitsi on my W7 home
premium system.

I was advised to try deleting/renaming jnportaudio.dll and issue was
resolved by renaming this dll.

···

On 29 May 2013 16:13, Anthony Papillion <papillion@gmail.com> wrote:

Hello Group,

A friend of mine is using the the latest version of Jitsi (downloaded
today) and it simply will not start. Upon starting the program, he
immediately gets a window saying "ouch, Jitsi seems to have crashed" and
offers him to restart it. When he does, the same thing happens.

He's on Windows XP SP3. Anyone know what might be going on? Also, if a
crash report would help, I'd happy to attach it but I need to know where
Jitsi for Windows stores the report.

Thanks,
Anthony

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

--
-------
inum: 883510009902611
sip: jungleboogie@sip2sip.info


#3

Windows' Event Viewer may reveal an error event containing details
about the crash.

A file hs_err_pid*.log may exist in %APPDATA%\Jitsi or %TEMP%.

If none of the above give a clue, rename/move away one by one any of
Jitsi's .dll files starting with jnportaudio.dll,
jnmsoutlookaddrbook.dll, jnwasapi.dll, jnwincoreaudio.dll.

···

2013/5/30 Anthony Papillion <papillion@gmail.com>:

Also, if a
crash report would help, I'd happy to attach it but I need to know where
Jitsi for Windows stores the report.


#4

Would it make sense to wrap all our loadLibrary calls into a function that checks whether the last load attempt was unsuccessful and stop loading it a second time to avoid the crash? (Perhaps asking the user to automatically collect logs).
Noting this into the props-file along with the version number would ensure that a newer release would be tried again.

Ingo

···

Le 30.05.2013 à 01:33, "Lyubomir Marinov" <lyubomir.marinov@jitsi.org> a écrit :

2013/5/30 Anthony Papillion <papillion@gmail.com>:

Also, if a
crash report would help, I'd happy to attach it but I need to know where
Jitsi for Windows stores the report.

Windows' Event Viewer may reveal an error event containing details
about the crash.

A file hs_err_pid*.log may exist in %APPDATA%\Jitsi or %TEMP%.

If none of the above give a clue, rename/move away one by one any of
Jitsi's .dll files starting with ...


#5

Also, if a
crash report would help, I'd happy to attach it but I need to know where
Jitsi for Windows stores the report.

Windows' Event Viewer may reveal an error event containing details
about the crash.

A file hs_err_pid*.log may exist in %APPDATA%\Jitsi or %TEMP%.

If none of the above give a clue, rename/move away one by one any of
Jitsi's .dll files starting with ...

Would it make sense to wrap all our loadLibrary calls into a function that checks whether the last load attempt was unsuccessful and stop loading it a second time to avoid the crash? (Perhaps asking the user to automatically collect logs).
Noting this into the props-file along with the version number would ensure that a newer release would be tried again.

This seems like a very good idea, especially on windows where we have a restarting crash handler!

So what do you have in mind? Writing down a "attempting load for <libname><jitsi.version>" property every time we start loading the lib and removing it when we are done? Something like that?

Emil

···

On 30.05.13, 08:08, Ingo Bauersachs wrote:

Le 30.05.2013 à 01:33, "Lyubomir Marinov" <lyubomir.marinov@jitsi.org> a écrit :

2013/5/30 Anthony Papillion <papillion@gmail.com>:

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

--
https://jitsi.org


#6

Would it make sense to wrap all our loadLibrary calls into a function that
checks whether the last load attempt was unsuccessful and stop loading it a
second time to avoid the crash? (Perhaps asking the user to automatically
collect logs).
Noting this into the props-file along with the version number would ensure
that a newer release would be tried again.

This seems like a very good idea, especially on windows where we have a
restarting crash handler!

So what do you have in mind? Writing down a "attempting load for
<libname><jitsi.version>" property every time we start loading the lib
and removing it when we are done? Something like that?

Yes, just like that:

if (getProperty(libname) != version){
  setProperty(libname, version)
  loadLibrary(libname)
  removeProperty(libname)
}
else {
  msgbox "Oops with $libname. Try to load it anyway or keep disabled until next version is available?"
}

Ingo