Closed mdednev closed 7 months ago
plz enable beta, restart telegram and send crash id on next start and post id here.
plz enable beta, restart telegram and send crash id on next start and post id here.
Error log:
makc@maximus:Telegram$ ./Telegram
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
Scudo ERROR: CHECK failed @ /usr/src/tdesktop/Telegram/ThirdParty/scudo/list.h:219 (Next->Prev) == (X) ((u64)op1=140142787382080, (u64)op2=140142114241344)
Crash ID: 38dcb717-fda2-4bf2-b7c2f197-9a64b2cc
ApiId: 2040
Binary: Telegram
Launched: 20.02.2024 20:03:57
OpenGL: Enabled
OpenGL Renderer: [not-initialized]
Platform: Linux
UserTag: 52d3d073fa5f96ff
Version: 4015000
Caught signal 6 (SIGABRT) in thread 140142114244352
Google Breakpad caught a crash, minidump written in thread 140142114244352
Minidump: /home/makc/.local/share/TelegramDesktop/tdata/dumps/38dcb717-fda2-4bf2-b7c2f197-9a64b2cc.dmp
38dcb717-fda2-4bf2-b7c2f197-9a64b2cc
Did you send this report? Because I don't see it :(
Can you try once again, send the report and post the CrashID after that.
I've sent crash report once again. Crash report ID: 7a339b95-8467-45cc-41c43887-5ae4651e
Can you build tdesktop with ASAN? It looks like a memory corruption.
I could try to build, but I need the instructions.
That's quite a good question, I wasn't able to build with asan myself, it ends with a gcc crash.
I've got the same problem here on Debian Bookworm (Linux 6.1.0-17-amd64)
tried with remote proxy, doesn't crash for me, socks 5 proxy.
I've got the same problem here on Debian Bookworm (Linux 6.1.0-17-amd64)
can you try with 199.58.185.9 socks 5 port 4145?
Are you folks sure it's happening due to proxy?
Are you folks sure it's happening due to proxy?
Yes, I've tried to use Telegram for several hours on the same machine without proxy using 4G LTE mobile connection and there were no crashes. The only difference was proxy. So 99% that the issue is somehow related to proxy connection.
The only difference was proxy. So 99% that the issue is somehow related to proxy connection.
Can you reproduce with the proxy provided by @Aokromes? If not it means the problem is only with some ones which in turn means access to your proxy is needed for debugging.
I'm using CNTLM HTTP(S) proxy. Not Socks5, as @Aokromes suggests to try.
I've tried to setup and run tinyproxy, bound to the 127.0.0.1:3130 without direct access to global network and Telegram also crashes when I try to use this local HTTP proxy. So this is not only CNTLM issue, it seems that it's HTTP proxy interaction problem.
How long should I use the proxy? I found some but I don't get the crash yet. This might be related to exact system configuration so would be nice if someone prepared a VM image where this is reproducible (or made reproductions steps right from installing the system in a VM). If the issue won't get reproduced, it will be marked accordingly and closed eventually.
This issue has been automatically closed because no developer succeeded to reproduce the issue with the given reproduction steps. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you find what's missing to reproduce the issue so that we can investigate further.
Note that GitHub is a developer communication platform. If you're an ordinary user seeking for help, get to support crew via Settings -> Ask question
in the application.
Steps to reproduce
Expected behaviour
Running without crashes.
Actual behaviour
Telegram crashes after running for some time.
Operating system
Debian GNU/Linux 11 (bullseye)
Version of Telegram Desktop
4.15.0
Installation source
Static binary from official website
Crash ID
38dcb717-fda2-4bf2-b7c2f197-9a64b2cc
Logs