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

White screen #824

Open
byDoks opened this issue Jul 22, 2021 · 16 comments
Open

White screen #824

byDoks opened this issue Jul 22, 2021 · 16 comments
Labels

Comments

@byDoks
Copy link

byDoks commented Jul 22, 2021

Hello!
after updating Element to version 1.7.33, suddenly just a white screen began to appear, only reinstalling the Element application helps, previously this was in version 1.36, this was fixed in version 1.4.1 and everything was fine.
Please fix it.

we use on the desktop version
OS: Win Server 2012R2.

@kojid0
Copy link

kojid0 commented Jul 23, 2021

Can confirm that this has been fixed for me previously, but was re-introduced in version 1.7.33...

Using Ubuntu 20.04 (ZorinOS16)

@fockr
Copy link

fockr commented Jul 23, 2021

Same here. I noticed it after the last update. It usually switches to white screen after I start typing.

@byDoks
Copy link
Author

byDoks commented Jul 26, 2021

Hello!
after updating Element to version 1.7.33, suddenly just a white screen began to appear, only reinstalling the Element application helps, previously this was in version 1.36, this was fixed in version 1.4.1 and everything was fine.
Please fix it.

we use on the desktop version
OS: Win Server 2012R2.

when will you fix the problem? impossible to work ..((

@ygaeon
Copy link

ygaeon commented Jul 27, 2021

I can confirm this as well ... happened occasionally before, but now it's several times per hour.
OS: Linux 5.13.4-arch2-1

Any options I can pass to element-desktop to produce some useful logs, please let me know.

@germain-gg
Copy link
Contributor

Would anyone be able to share the logs in the developer console? That would help us figure out what is going on a bit more easily as I am not aware of anyone able to reproduce this one our end so far

@ygaeon
Copy link

ygaeon commented Jul 27, 2021

Would anyone be able to share the logs in the developer console? That would help us figure out what is going on a bit more easily as I am not aware of anyone able to reproduce this one our end so far

Would love to help out ... if you could point me to where I can learn how to enable the developer console on the element-desktop

@SimonBrandner
Copy link
Contributor

Would anyone be able to share the logs in the developer console? That would help us figure out what is going on a bit more easily as I am not aware of anyone able to reproduce this one our end so far

Would love to help out ... if you could point me to where I can learn how to enable the developer console on the element-desktop

Press Ctrl+Shift+I

@byDoks
Copy link
Author

byDoks commented Jul 28, 2021

Would anyone be able to share the logs in the developer console? That would help us figure out what is going on a bit more easily as I am not aware of anyone able to reproduce this one our end so far

Would love to help out ... if you could point me to where I can learn how to enable the developer console on the element-desktop

Press Ctrl+Shift+I

It won't work when the element screen goes white, the console doesn't work either.
https://prnt.sc/1gmvezq

@fockr
Copy link

fockr commented Jul 28, 2021

Update: now it works except for one username in my list. When I try to text this user the window turns white. I have no clue why. He is on the same server like me.

@ygaeon
Copy link

ygaeon commented Jul 28, 2021

I've run the client since yesterday and only blanked once (not "white" in my case, this time though, maybe because I had the console open?).
I do, however, unlike @byDoks , have some logs. Unfortunately, none of them are really anything useful (only things like Updating homeserver-configured integration managers..., or Persisting sync data up to ....)

I see one error, (failed promise), but it was way before the screen blanked. I'll copy it in here anyway, just in case:

EventIndex.ts:342 Uncaught (in promise) TypeError: Cannot read property 'rawDisplayName' of null
    at m.addLiveEventToIndex (EventIndex.ts:342)
    at K.<anonymous> (EventIndex.ts:232)
    at K.s.emit (events.js:158)
    at h.t (ReEmitter.ts:45)
    at h.s.emit (events.js:158)
    at h.decryptionLoop (event.ts:683)
addLiveEventToIndex @ EventIndex.ts:342
(anonymous) @ EventIndex.ts:232
s.emit @ events.js:158
t @ ReEmitter.ts:45
s.emit @ events.js:158
decryptionLoop @ event.ts:683
async function (async)
(anonymous) @ EventIndex.ts:232
s.emit @ events.js:158
t @ ReEmitter.ts:45
s.emit @ events.js:158
decryptionLoop @ event.ts:683
async function (async)
decryptionLoop @ event.ts:595
attemptDecryption @ event.ts:545
decryptEventIfNeeded @ client.ts:5792
onEvent @ Notifier.ts:333
s.emit @ events.js:158
h @ sync.ts:1306
O @ utils.ts:463
async function (async)
O @ utils.ts:463
(anonymous) @ sync.ts:1323
async function (async)
(anonymous) @ sync.ts:1322
O @ utils.ts:463
async function (async)
O @ utils.ts:463
processSyncResponse @ sync.ts:1188
_sync @ sync.ts:811
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854
async function (async)
_sync @ sync.ts:778
_sync @ sync.ts:854

@xobs
Copy link

xobs commented Nov 11, 2021

I got the white screen as mentioned here. I pressed Ctrl+Shift+I, which popped up this window:
image

The Console tab has no data, so I'm not sure what more information can be added.

@xobs
Copy link

xobs commented Nov 11, 2021

Here's what it looks like when I detach the developer tools window:
image

@AppTester7
Copy link

AppTester7 commented Nov 15, 2021

ELEMENT:

*Occasionally goes to a white screen, even if i dont interact with element

*Sometimes this happens upon startup

*Sometimes when Im going to a different room it happens

I can get the developer console to come up with ctrl+shift+i but DevTools reports
that it has been disconnected from the page. I have no option but to restart the client.

Im personally convinced this is a timing related issue, as the apparently intermittancy of this issue
noting things like occasional interaction by the user to do certain things (like going into a room or a DM)
seem to occasionally trigger this 'white window' issue
Does any one here think this could be an issue with timing/sync issues, like an IRQ (Interrupt Request) issue ?

OS: Linux - OpenSUSE Tumbleweed
DE: KDE Plasma Wayland
Element version: 1.9.2
Olm version: 3.2.3

@novocaine
Copy link
Contributor

novocaine commented Nov 19, 2021

A white screen means Electron's renderer process has crashed. Element code can't crash that process as it runs in a container - there's some problem with either Electron or your system (drivers, run out of resources etc).

You might be able to get some extra logs from your system about the crash to pinpoint the issue; on linux you can enable core dumps and load them up in GDB if you are keen.

Upstream issue: electron/electron#2357

@AppTester7
Copy link

I will provide a log if someone specifies exactly what log they want
need more specific info than just 'some extra logs from your system' - too vague
what logs, and how do i go and get them
Also, what is GDB

@t3chguy
Copy link
Member

t3chguy commented Nov 15, 2022

Related element-hq/element-web#22477

@t3chguy t3chguy transferred this issue from element-hq/element-web Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

10 participants