8000 Electron 1.8.x arm releases are broken · Issue #12329 · electron/electron · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Electron 1.8.x arm releases are broken #12329

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.

Sign up for GitHub

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

Jump to bottom
Closed
jkleinsc opened this issue Mar 16, 2018 · 8 comments
Closed

Electron 1.8.x arm releases are broken #12329

jkleinsc opened this issue Mar 16, 2018 · 8 comments
Labels
2-0-x blocked/need-info ❌ Cannot proceed without more information bug/regression ↩️ A new version of Electron broke something platform/linux version/1.8.x

Comments

@jkleinsc
Copy link
Member
  • Electron version: 1.8.2, 1.8.3, 1.8.4
  • Operating system: Raspbian GNU/Linux 9 (stretch)

Expected behavior

Running electron with no arguments should display the Electron startup screen.

Actual behavior

An empty screen is displayed:
electron184

Also when running with ELECTRON_ENABLE_LOGGING=true and ELECTRON_ENABLE_STACK_DUMPING=true, stderr displays the following:

[1735:0316/141145.459308:WARNING:audio_manager.cc(293)] Multiple instances of AudioManager detected
[1735:0316/141145.459830:WARNING:audio_manager.cc(254)] Multiple instances of AudioManager detected
[1759:0316/141146.574389:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process. 
Received signal 4 <unknown> 000000775f5e
#0 0x0000017d5f52 (/home/pi/Downloads/electron184/electron+0x17d5f51)
#1 0x0000017d5e42 (/home/pi/Downloads/electron184/electron+0x17d5e41)
#2 0x000074b226c0 (/lib/arm-linux-gnueabihf/libc-2.24.so+0x2c6bf)
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[1735:0316/141146.615271:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[1735:0316/141146.616247:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[1735:0316/141146.616998:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[1735:0316/141146.619423:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[1735:0316/141146.619938:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.

I also tested the 2.0.0-beta.4 release and it worked correctly
electron2b4

How to reproduce

  1. Download a 1.8.x arm release (electron-v1.8.4-linux-armv7l.zip) on a Raspberry PI 2 or a Raspberry PI 3 running a 32 bit OS
  2. Unzip the archive
  3. Run electron from the archive with no args.
@jkleinsc jkleinsc added bug/regression ↩️ A new version of Electron broke something version/1.8.x labels Mar 16, 2018
@jkleinsc jkleinsc mentioned this issue Mar 16, 2018
Closed
@RebelSyntax
Copy link
RebelSyntax commented Mar 19, 2018 •
edited
Loading

If I have a chance later, I'll post up some logs. I have the same platform setup as @jkleinsc. I tried the latest 1.7 and had same results as the 1.8.x I had to go back to 1.7.11.

Maybe that narrows it down some on where to start looking.

@xiaods
Copy link
xiaods commented Apr 2, 2018

any process?

@zcbenz
Copy link
Contributor
zcbenz commented Apr 3, 2018

From the comments:

  • 1.8.1 works
  • 1.8.2 does not work
  • 1.7.11 works
  • 1.7.12 does not work.

It seems that 8b6aa22 is responsible for the problem, but the code looks very innocent to me.

@brubbel
Copy link
brubbel commented Apr 4, 2018 •
edited
Loading

#2 0x000074b226c0 (/lib/arm-linux-gnueabihf/libc-2.24.so+0x2c6bf)

Possibly some versions were compiled against libc-2.19.so while debian stretch seems to use
libc-2.24.so.

debian jessie (this seems related to 8b6aa22)

addr2line -j .text -e /lib/arm-linux-gnueabihf/libc-2.19.so  0x2c6bf
/build/glibc-g3vikB/glibc-2.19/stdio-common/vfprintf.c:1642

debian stretch:

addr2line -j .text -e /lib/arm-linux-gnueabihf/libc-2.24.so  0x2c6bf
/build/glibc-HsYnUB/glibc-2.24/stdio-common/_i18n_number.h:62

cfr:
https://packages.debian.org/jessie/armhf/libc6/filelist
https://packages.debian.org/stretch/armhf/libc6/filelist

@ghost
Copy link
ghost commented May 29, 2018

Happens to me using raspbian 9.4 Stretch and electron@2.0.2.

@brubbel
Copy link
brubbel commented Jul 28, 2018 •
edited
Loading

Note:
RPI3B, Debian Stretch, within docker container (i.e. no OpenGL), electron-quick-start with electron@2.0.5 works as explained here by setting app.disableHardwareAcceleration(); at this location.

Or run just run electron --disable-gpu as described here.

Alternatively, installing libgl1-mesa-dri (apt install --no-install-recommends libgl1-mesa-dri) also works, without any of the above flags.

@Kagami Kagami mentioned this issue Aug 11, 2018
Closed
@sofianguy sofianguy added the 2-0-x label Jan 7, 2019
@molingyu molingyu mentioned this issue Feb 18, 2019
Closed
@miniak miniak closed this as completed May 18, 2019
@miniak miniak reopened this May 18, 2019
@sofianguy
Copy link
Contributor

@jkleinsc is this still a problem in later versions of electron?

@sofianguy sofianguy added the blocked/need-info ❌ Cannot proceed without more information label Aug 9, 2019
@jkleinsc
Copy link
Member Author
jkleinsc commented Aug 9, 2019

@sofianguy no, I'll close this.

@jkleinsc jkleinsc closed this as completed Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2-0-x blocked/need-info ❌ Cannot proceed without more information bug/regression ↩️ A new version of Electron broke something platform/linux version/1.8.x
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@xiaods @jkleinsc @zcbenz @miniak @sofianguy @brubbel @RebelSyntax
0