Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAC: Crashes when openning a file/section via the TOC #3792

Open
d3vf1x opened this issue Sep 11, 2024 · 13 comments
Open

MAC: Crashes when openning a file/section via the TOC #3792

d3vf1x opened this issue Sep 11, 2024 · 13 comments

Comments

@d3vf1x
Copy link

d3vf1x commented Sep 11, 2024

From time to time the textstudio app will crash wehn navigating to a section via the sidbar toc menu.
But it is only a specific section, all other will work fine.
Then after a while this section will also work again.
But once it crashes it will crash consistently, meaning after a restart of the application I can click the same section again and it will crash again.

Environment

TeXstudio 4.8.2 (git 4.8.2)
Using Qt Version 6.7.2, compiled with Qt 6.7.2 R

Crash report:
https://pastebin.com/r2300x3z

Expected behavior

Click on the Section should open the corresponding file and jump to the section in it

Actual behavior

Texstudio will crash. Even after restart the same error will show again.

@sunderme
Copy link
Member

a reproducible test case would be helpful...

@d3vf1x
Copy link
Author

d3vf1x commented Sep 13, 2024

I cannot reproduce it reliably and i don't want to copy my whole project...
Any other idea?

@sunderme
Copy link
Member

no way around a test case (or you can debug it yourself)
you can send larger test cases also directly to me (sunderme@gmx.de)

@d3vf1x
Copy link
Author

d3vf1x commented Sep 19, 2024

I cannot find a minimal example that will "reliable" crash...
Is there another way to extract useful information for you?

@sunderme
Copy link
Member

my guess is that the actual bug occurs way before the actual crash.
Are you closing documents before the crash happens ?

@d3vf1x
Copy link
Author

d3vf1x commented Sep 19, 2024

No 100% sure but i would say no.
It is also consistent even after a restart of the program.
When I click on the same section again it will crash again.
But after some time and changes to some files I can click on the same section again and it will not crash...
Thats what it makes so hard to reproduce.
But most of the time i have about 18-12 tabs open.

@sunderme
Copy link
Member

sunderme commented Sep 19, 2024

That I don't understand.
When you are at a state that it crashes after a restart when pressing on a certain section, it does not crash the next time ?

@d3vf1x
Copy link
Author

d3vf1x commented Sep 19, 2024

Sorry for any confusion.

It will crash when I click on a particular entry of the Sidebar Window TOC.
Then after a restart I can click on the same Entry and it will crash again.
This can now be repeated indefinitely.

Sometimes it is only on entry that leads to a crash and sometimes there are multiple.

But it is never deterministic (as far as I understand) which entry will lead to a crash.

@sunderme
Copy link
Member

sunderme commented Sep 19, 2024

And the crashing document(s) can't be used as a test case ? E.g. load these documents and press that section ?

@d3vf1x
Copy link
Author

d3vf1x commented Sep 19, 2024

Its a work document i'm not allowed to share unfortunately.
I tried removing any relevant pages to be able to share it but every time I tried this after a crash, the bug will disappear.
It seems like altering the content of the pages will "fix" the bug tempoarly.

The funny thing is that I can open the relevant page (the page with the section that will cause the crash) manually without crashing.

@sunderme
Copy link
Member

can you try do disable document caching (options/editor/cache document for faster reopening)

@d3vf1x
Copy link
Author

d3vf1x commented Sep 21, 2024

I deactived it.
I will give it a try and report how it is going.

@d3vf1x
Copy link
Author

d3vf1x commented Sep 24, 2024

No crashes since then.
This seems to be the "fix"

Thanks for your help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants