Illegal instruction crash in non-sse2 architectures

[Nephiel]

On AMD Athlon XP 2200+, Telegram crashes on startup with "Illegal instruction".
These processors are old and do not support the sse2 instruction set.
Does any component or library of Telegram require sse2?

[telegramdesktop]

@Nephiel Perhaps ffmpeg or openal do. Is there a crash dump in tdumps folder near Telegram.exe?

[Nephiel]

I'm not sure, I was using the 32-bit Linux version on Debian Jessie. Will try again later today.

[Nephiel]

Just tried it again. Running the Telegram binary from the commandline results in

Illegal instruction

There doesn't seem to be any crash dump. I tried running it with gdb, the output is

Starting program: /home/nephiel/temp/Telegram/Telegram 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x080a687b in _GLOBAL__sub_I_qguiapplication.cpp ()

Also tried running the Updater binary, it terminates immediately with no output at all, and gdb reports it exited normally. No crash dumps either.

[telegramdesktop]

@Nephiel The line about crash dumps was about launching from Windows. "catchsegv Telegram" from Terminal? On Linux, it should show the backtrace.

[GregMay]

I can confirm this consistent crash on Windows XP also, apparently if the system doesn't have SSE2. The telegram.exe program consistently crashes at address 0x000700a0 with two totally different machines (AMD PC vs Intel Laptop).

Could this be possibly something to do with the Qt toolkit requiring SSE2? It might need to be compiled with the requirement disabled for Telegram to work properly with older machines.

I did report this via support on the app, but my report didn't seem to be forwarded...

[Nephiel]

Tried catchsegv, no trace at all.

nephiel@athlonxp:~/Downloads/Telegram$ catchsegv ./Telegram
Illegal instruction

[Zenexer]

It's receiving SIGILL, not SIGSEGV, so catchsegv isn't going to do anything.

The subroutine referred to in the error is probably in Qt's qguiapplication.cpp.

[ghost]

Hey there!

We're automatically closing this issue since there was no activity in this issue since 382 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.

Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

_{(Please note that this is an automated comment.)}

[sunny-o]

I have the same crash on Athlon w/o SSE2 support, so I hope that you'll reopen this issue.

[mirh]

https://forum.qt.io/topic/16237/regarding-qt-configuration-and-sse-sse2
This is probably newer MSVC versions optimizing for SSE2 by default.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.