TeXstudio has CRASHED due to a unknown at ...

Question

TeXstudio has CRASHED due to a unknown at ...

Closed this issue 2 years ago · 26 comments

(This is a duplicate of #2560, which is already marked closed. I try to provide more information here.)

Environment

TeXstudio: 4.3.1, 64 bit, installer version from the website
Qt: 5.15.2
OS: Windows 10, 64 bit, current updates
TeX distribution: TeXLive

Reproduces on two different machines. German laguage version is shown in the screenshot, which is what is default on my system, but I reproduced it with the English display language by actively changing it in the settings.

Expected behavior

TeXStudio does not "crash".

Actual behavior

TeXStudio "crashes" on startup with a popup ("crashes" in quotes, see below).
"TeXstudio has CRASHED due to a unknown at ..."

After that I see some hexadecimal address (e.g. "7ff959655bb6" or "71c640") which sometimes stays identical when restarting the software in quick succession (but I have seen vastly different addresses on the same machine).

There is also a second popup (appearing a bit later) that I can close with the "Cancel" button with and seems to have an empty textbox or a progress bar.

When I click "Yes, try to recover" I can continue working (but I didn't try for long; I managed to change the display language for instance).

In this case there will another "TeXstudio has CRASHED due to a unknown at ..." popup upon exiting TeXStudio (with another address).

The "texstudio_backtrace" file contains:

unknown at 71c640 (TXS-Version 4.3.1 R )
[bt] 000000000064dd70  ??? error: 487

How to reproduce

I cleaned everything in "%appdata%/TeXStudio", so I presume just launch the described version after a clean install and it should "crash". No other reproduction steps required.

Other things

I do not have this problem with 4.3.0 (Qt 5.15.2) and went back to this version for now. In #2560 it was mentioned that the 4.3.1 Qt6 version is not affected.
I should also mention, that I originally pulled in the version through chocolatey, but then uninstalled these versions and tried the installers from the website. I used choclatey to roll back to 4.3.0.

Thanks for this great software!

sunderme commented 2 years ago

miktex ?

Answer 1 · 2022-09-04T17:01:41.000Z

well, no.
The image clearly shows that you are at least restoring a file/session.
I have not seen or heard it crash just by starting clean, so something is missing.

Answer 2 · 2022-09-04T17:02:23.000Z

any particular reason to use qt5 ?

Answer 3 · 2022-09-04T17:13:37.000Z

well, no. The image clearly shows that you are at least restoring a file/session. I have not seen or heard it crash just by starting clean, so something is missing.

Was confused now too, because I was certain that it was a clean start^^ However, what I did was double-clicking a file (i.e. opening TeXStudio with a filename as cmd line argument).

Just tried it again (clean) without opening any file and then it does indeed not "crash". It "crashes" as soon as the first file gets opened, though.

any particular reason to use qt5 ?

It is the only option offered through the chocolatey package manager afaik (see here), which I use to keep software up to date.

Answer 4 · 2022-09-04T17:18:55.000Z

then I need that file at least (or a stripped down version which crashes)

Answer 5 · 2022-09-04T17:20:44.000Z

You are right. I'll will create such a file an be right back :)

Answer 6 · 2022-09-04T17:21:49.000Z

(I just tried it with an empty file and it did not "crash", hence there must be something about all of the LaTeX files that I was using. Did never occured to me that this could be the issue.)

Answer 7 · 2022-09-04T17:36:11.000Z

I have the same problem on v4.3.1 Qt Version 5.15.2. How can I start TeXstudio without it opening the last file I had open before that issue ocurred?

Edit: Just downgraded to v4.3.0 via chocolatey and can confirm the issue is gone.

Answer 8 · 2022-09-04T17:52:40.000Z

there is a "restore session at startup" option

Answer 9 · 2022-09-04T17:52:47.000Z

Took me a while to strip a file down.
Rename the attached file to "*.tex". Opening it in TeXStudio 4.3.1 always crashes for me.

crash.txt

File listing (utf-8, windows linefeeds CR-LF):

\documentclass[12pt]{scrartcl} %
\usepackage{thispackagedoesnotexist} %

Answer 10 · 2022-09-04T17:55:29.000Z

TeXLive 2022 full (default settings just without the shipped editor).
Quite recent updates.

Answer 11 · 2022-09-04T17:58:41.000Z

I'm sorry... ~~This file just stopped crashing for me...~~ (see comment below) Is there something persistent except the %appdata%/texstudio folder?

I always deleted this folder and tried to open the file. I can post a much longer version of the file which I actually use. Just have to remove some confidential stuff.

Answer 12 · 2022-09-04T18:08:29.000Z

Nevermind, the file posted above does still crash, but only sometimes (in particular on the very first start after deleting %appdata%\texstudio)?

Here is a longer version much more related to what I'm actually working on. This crashes much more reliably.
iopart and iopams are not part of a standard LaTeX distribution, hence I tried to strip them (they are part of the IOP LaTeX template)
Notice, that I don't have iopart or iopams in the folder where I have crashlong.tex.

crashlong.txt
(delete %appdata%/texstudio, rename to crashlong.tex in an empty folder and open in texstudio)

Answer 13 · 2022-09-04T18:29:32.000Z

no, %appdata%... is the only persistent
does it also happen with txs qt6 (try with portable version)

Answer 14 · 2022-09-04T18:44:45.000Z

you could try to remove packageCache.dat in the %appdata%... directory.

Answer 15 · 2022-09-04T18:53:03.000Z

Okay. Took me a moment, since I did get confused with all the versions in the middle.

For comparibility I just updated all texlive full 2022 packages to the most recent version.
I use the portable version of TeXStudio, except for 4.3.0 where I can't find it on the website, there I use the installed version from chocolatey.
Here are the steps I take:

Delete the %appdata%/texstudio directory (I re-extracted the portable ZIP files for each test, since I think there is something strored in the config dir?)
Open either version of TeXStudio directly
No version crashes at this stage
Open the short, two-liner crash.tex and crashlong.tex in an otherwise empty directoy

Results:

TS 4.3.1 Qt5: crashlong.tex crashes, crash.tex is fine.
TS 4.3.1 Qt6: None of the files crashes
TS 4.3.0 Qt5: None of the files crashes

Answer 16 · 2022-09-04T18:59:39.000Z

you could try to remove packageCache.dat in the %appdata%... directory.

I did, but with no observed effect. The installed TS 4.3.1 Qt5 still crashes with both supplied files (in case of the short file at least sometimes)

Answer 17 · 2022-09-04T19:00:30.000Z

unfortunately it does not crash on linux/qt5 which makes debugging tedious.

Answer 18 · 2022-09-04T19:04:07.000Z

Yes... I also noticed that it was very hard to even create a file that "crashes" reliably as you can see from my posts above.

Is there any debug mode that can be enabled in windows to obtain verbose logging on my end?

Answer 19 · 2022-09-04T19:06:38.000Z

unfortunately there is not. You could compile txs yourself (see wiki) and run it in a debugger.
But it looks like it is related to qt5/mxe and maybe it is time to retire that build.

Answer 20 · 2022-09-04T19:06:56.000Z

(mxe has not been updated for some time...)

Answer 21 · 2022-09-04T19:12:41.000Z

As long as the Qt6 version works, I'd say it's probably not worth the effort...

I'd much rather like to have the chocolatey version switch to Qt6.
I'll probably contact the maintainer there and ask them to add this as an option or better the default?

Would you say that the Qt5 version is deprecated anyways?

Answer 22 · 2022-09-04T19:13:39.000Z

yes,qt5 is deprecated, qt6 is the default.

Answer 23 · 2022-09-04T19:16:38.000Z

Okay. Then I'll write to the maintainer of the chocolatey package and refer them to this thread.

Thanks for your help and thoughts! :)

Answer 24 · 2022-09-13T19:00:33.000Z

assume mxe/qt5 issue

Answer 25 · 2022-10-08T18:58:54.000Z

Just downgraded to v4.3.0 via chocolatey and can confirm the issue is gone.

This solved the issue for me!