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

Stable crashes #1793

Closed
aulnv opened this issue Jul 23, 2024 · 6 comments
Closed

Stable crashes #1793

aulnv opened this issue Jul 23, 2024 · 6 comments
Labels
A-Electron O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Z-Platform-Specific

Comments

@aulnv
Copy link

aulnv commented Jul 23, 2024

Steps to reproduce

Hello. Well sorry for my eng I'll try use right terms
Since next to 1.11.57 (not since 1.11.57) Element started to crash as soon as I'd begging to use it more actively, like chatting or explore/looking for anything in room history. Now is point, it is unbearable not to pay attention to the app crashes that are too much frequent. It just happened again while I was chatting in two rooms in parallel, distracted by other devices, so it happened for the umpteenth time in an hour. It always looks like unexpected window collapse but window stay opened without any interface details + apple report window
Ah when once it self-updated to 1.11.58 and next builds I locked app to stay on 1.11.57. And nowadays it always asks mac-password to install update and I successfully skip it.
I have exactly the same problem on my MacBook Pro a1398, the App also crashes and show empty white tab. By the way, the first crash happened on that MacBook, it was the next build after 1.11.57, the application immediately closed when trying to open it and the apple report window appeared. It seemed to me that the MacBook can't run with 2+ programs in parallel and I got iMac which also has the same crashes of Element.
When this white window is opened after crash, I can get about app tab, but it doesn't respond to anymore like clicks to preferences etc
Now I could close and open App but not for a long bcs 1.11.57 was stable but now it's not.
that is what I see every time and became burning inside
Снимок экрана 2024-07-23 в 23 34 26
last crash apple report element.txt
well before submit new issue I tried to reopen app and this time it immediately crashed and showed a white tab again (before that, the usual interface with rooms and space was loaded for a couple of seconds)
close white tab and shutdown the app (cmd q) > click element icon to open > loading but not for a long and get crash again
last report crash on start.txt

one else
report .txt

Outcome

What did you expect?

stop crashes

What happened instead?

crashes
sorry I can't understand this questions alright

Operating system

MacOs

Application version

1.11.57

How did you install the app?

element.io

Homeserver

https://matrix-client.matrix.org

Will you send logs?

Yes
I am trying to send logs, but the process is interrupted by a white window

@aulnv aulnv added the T-Defect label Jul 23, 2024
@dosubot dosubot bot added A-Electron S-Critical Prevents work, causes data loss and/or has no workaround labels Jul 23, 2024
@aulnv aulnv changed the title Stable shutdowns Stable crashes Jul 23, 2024
@richvdh
Copy link
Member

richvdh commented Jul 24, 2024

Could be related to #691. Have you tried a recent version?

@richvdh richvdh added the O-Uncommon Most users are unlikely to come across this or unexpected workflow label Jul 24, 2024
@dbkr
Copy link
Member

dbkr commented Jul 29, 2024

The crashes here are all on Element trying to confirm whether it should quit or not, so thesemay be unrelated if you say the app is crashing as part of normal usage. What version of MacOS are you on? It looks old.

@t3chguy
Copy link
Member

t3chguy commented Jul 29, 2024

What version of MacOS are you on? It looks old.

If you're basing that on the UA in the rageshake then that's because macOS lies. https://forums.developer.apple.com/forums/thread/699953 the same applies to all browsers on macOS

@aulnv
Copy link
Author

aulnv commented Sep 5, 2024

Thanks, I find issues like that, old macos are compatible with builds before 1.11.57

@richvdh
Copy link
Member

richvdh commented Sep 5, 2024

I'm struggling to understand what the issue actually is here: which versions work ok, which versions do not work, and what, exactly, happens when you try the current version (1.11.76)?

@richvdh
Copy link
Member

richvdh commented Sep 11, 2024

Without clearer information, I suspect this is a duplicate of #1505.

@richvdh richvdh closed this as completed Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Electron O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Z-Platform-Specific
Projects
None yet
Development

No branches or pull requests

4 participants