Hey I just wanted to report to you guys that there seems to be an Electron issue with the system package that someone will need to fix, the developers at Electron said I should report it to you guys.
Please lookup the maintainer for the package in question.
$ pacman -Si electron34 | grep -e Packager -e Version
sure thing
Version : 34.3.3-1
Packager : Manjaro Build Server <build@manjaro.org>
In the x86 extra repo - the package is version 34.5.0-2
$ mbn info electron34 -q | grep -e Packager -e Version
Version : 34.5.0-2
Packager : Caleb Maclennan <alerque@archlinux.org>
Version : 34.5.0-2
Packager : Caleb Maclennan <alerque@archlinux.org>
Version : 34.5.0-2
Packager : Caleb Maclennan <alerque@archlinux.org>
Version : 34.5.0-2
Packager : Caleb Maclennan <alerque@archlinux.org>
The package is maintained by Mark - but it seems the PKGBUILD is not used - the version does not match the version on your system 34.3.3-1
We will have to ask @Yochanan about this.
Can you please check if you still have that issue if you start the app with the following flag added:
--js-flags=--no-decommit-pooled-pages
I’ve just pushed electron34 34.5.0-1 to arm-unstable.
I can confirm that stops it from happening on this version, I will also do a update since @Yochanan pushed 34.5.0-1 to unstable which is what I am on.
I updated but sadly I am still running into the issue and using--js-flags=--no-decommit-pooled-pages as @Sam_Fisher suggested stops it from happening.
Also on Youtube the player buttons all show the fullscreen button until you put your mouse over it in general even with electron from npm, not sure what that’s about lol 
So I am thinking it could be one of the components you are using.
As I known and you too know, variables in javascript are global - even if you think they are not 
If I understand it correct - Electron is a huge javascript application - build using the Chrome engine.
Just a few days ago I had an issue with a company PWA I am maintaining, built using Blazor WASM.
I still have to figure out why the app stalled only for users using Safari on iPad - android and computer users were not affected.
It turned out that my variable naming in the specific part of the app could be the culprit because when I restricted the scope of the variables and renamed them using underscore _variableName and transpiled the whole #! - the problem went away.
1 Like
You can let upstream know all we do is package the official linux-arm64 binary release–the same way as the AUR electronXX-bin packages do.
Sure it has been done
I would assume the issue is caused by neither electron nor chromium. You mention in your bug report that you are on an Apple machine using an arm chip. Do you use the generic arm image of manjaro? I am on a RPI5, it is also an arm device but it has a different manjaro arm build. We also do have issues with the chromium being not compatible with 16k page size kernel (which is what we have). So i just assumed maybe other arm releases of manjaro are also 16k kernel and that is why i asked you to try the command line argument. Seeing that it is a youtube app that you are trying to run, I need to use this flag on both “chromium” itself and the “freetube” (also a youtube player) app that i am using which is also chromium based (it also uses electron). Do you use chromium also? Because it would cause similar issues without the command line argument that i have mentioned.
I am not really knowledgeable about the topic of kernel page sizes and their compatibility with some programs but this is the root cause of our issues and at least we have some ways to remedy chromium itself and chromium based apps. I haven’t encountered any other issues with any other programs that i have been using.
I’m sorry but I never said I was on Apple Hardware, I am on my Raspberry pi 5 8gb on Manjaro unstable branch. 
I haven’t tested Chrome in a while but all my apps using electron that support arm64 from npm don’t have this issue so I am not sure if it has to do with page size or not and couldn’t say either tho I could test the latest version of Chrome on my pi 5.
Real easy to find out. Just boot your pi5 on the linux-rpi4 4k kernel.
/boot/config.txt ( Make sure linux-rpi4 is installed):
kernel=kernel8.img