Freshly installed Jami crashes when clicking on "Create Account"

changed the description

assigned to @mzhang

Thank you for reporting,

If possible, could you send us some dump files generated by the newest release?

It would helpful for us to solve the mystery.

Best, Ming

I would do that, but you need to tell me where those dump files are located or how I can make sure that they get generated in the first place.

Yes,

Can you take a look at this? https://helgeklein.com/blog/2018/10/creating-an-application-crash-dump/

It has the details about how to generate a dump file.

Thanks for the link! I attached the crash dump file. In it's original state it was 13 MiB so I had to compress it into a 7z-file to be able to attach it here.Jami.exe.4108.dmp.7z Btw in case it isn't obvious from the dump file I used a freshly installed Jami which I installed via a freshly downloaded jami.beta.x64.msi.

Hi, thank you for that,

We will take a look at this asap

fixed?

@sblin Sadly not. I've given up on Jami consequently since on two of my three Linux machines it also crashes to desktop although at a later stage.

@sblin was there a follow up issue or other fix for this? A colleague of mine (on windows) couldn't participate in our jami evaluation, because of this early crash. If this is an ongoing investigation, I might be able to point him here to help investigating the cause (can't promis this, it's not my time). I'm windows free and the qt client is stable (for now) on my system

I think we can close this issue since it appeared on Windows 7?

Since this year Jami uses Qt6 and Qt6 only supports Windows 10 & 11 64-bit.

So this is a won't-fix.

EDIT: Unless someone can reproduce on any Linux-Distro or Windows 10,11 (64-bit).

i still have the same problem on win 10 OS

It happened today:

Windows 10 / 64bit Version 21H2 Jami Client: 1.0.8308

I have no issues using Jami Version 202209300958 but I didn't try to create a new account.

Where did you get the number of the client? I just find a Jami Version.

(You can find all download links here:https://dl.jami.net/windows/ )

I didn't I simply relay messages for now

Maybe that is the server reported version, I don't know, I'll ask

Edit: That will be the jami version, not the client. The windows client was downloaded here https://jami.net/download-jami-windows/ about 3 hours ago.

This is a crash dump zip. Created with the latest released version (30. September 2022 14:07)

Jami.exe.8312.zip

The beta version crashes as well - I'll try to get a crash dump for this as well. Edit: Here it is: Jami-beta.exe.12196.zip

Thanks to my Colleague for trying out different versions and procuring the crash-dumps

I hope that helps you find the error. As of now I cannot recommend to evaluate Jami further at our end - almost every Desktop is a windows machine.

Can you actually use the option "Restore an account from Backup" (If you have any backup)? Or use the option "Link this device using an existing account" (If you have a smartphone and used it to create an account)?

Anyway thanks for the zip!

Probably - but I don't want to impose more on my colleagues time - its vacation time there; I don't have a windows machine at my disposal; cross-platform use of jami was the big point for me (f-droid availability a big plus); Maybe when they're back, and this is still a mystery, we can experiment a bit more.

OK ... Thanks for doing these tests! I hope the developers will fix this issue as soon as possible.

Just a guess: As soon as you might have time: Does it change anything if you launch Jami as an admin and/or run Jami in compatibility mode?

Maybe this might help: https://www.guidingtech.com/top-ways-to-fix-app-crashes-on-windows-10/

unassigned @mzhang

@tomterl Sadly nobody here is able to reproduce on any windows device we got.

The dump gives no useful information. (Only "The thread tried to execute an invalid instruction.").

It can be rather a system incompatibility, something badly installed, or a Qt bug. What is the hardware on this device (CPU/GPU)? I don't know if on windows there is something like a system log, maybe the invalid instruction used can be found here