-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Random crash in DocTab #3909
Comments
Re-opening this because I encountered it again in develop (v2.3.6-0.20230618081107-a984816deecd)
|
#4009 |
I think we are still missing code to reproduce this error? |
I tried removing all and adding new tab but could not cause the crash. |
There is an additional interaction (and thread) through your use of |
The OnClosing function most of the time does nothing, it is built like this because certain ITab must do cleanup when closed. The OnClosed method does nearly nothing involving fyne, only database access, sometimes dialog display. In the particular case of the last crash encountered, the OnClosed does strictly nothing other than directly calling the function passed to it. But I will investigate more in this direction... |
Always happening... Here is the code responsible for managing docTabs in my application: https://pastebin.com/56DWJG2R By the way, the crash not only happens on tab closing, but also when adding the very first tab at application launch. |
Would it be possible to just add a simple check in the begining of docTabsRenderer.scrollToSelected to see if r.docTabs.current is not out of bound of buttons.Objects? |
Something like this? |
Landing for release branch |
Checklist
Describe the bug
DocTab randomly crashing when selecting an Item
How to reproduce
I have no idea why sometimes it happens, and sometimes no...
Screenshots
Example code
I have a complexe code base, I could not reproduce the bug with simple code.
Fyne version
develop v2.3.4-rc1.0.20230516195251-56dd0f3e0f32
Go compiler version
1.20
Operating system and version
Windows 10
Additional Information
No response
The text was updated successfully, but these errors were encountered: