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

Regression on Android build #32161

Closed
Gae24 opened this issue Apr 26, 2024 · 5 comments · Fixed by #32298
Closed

Regression on Android build #32161

Gae24 opened this issue Apr 26, 2024 · 5 comments · Fixed by #32298
Labels
P-android Android devices

Comments

@Gae24
Copy link
Contributor

Gae24 commented Apr 26, 2024

Describe the bug:
After the latest changes to the font system the android app doesn't work anymore.

Couldn't open font file!: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'Script(1,1)' panicked at components/gfx/font_cache_thread.rs:645:13:
Failed to receive a response from live font cache
thread 'Script(1,1)' panicked at components/gfx/font_cache_thread.rs:613:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Style#1' panicked at components/gfx/font_cache_thread.rs:613:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Style#2' panicked at components/gfx/font_cache_thread.rs:639:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Style#1' panicked at components/gfx/font_cache_thread.rs:613:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Script(1,1)' panicked at components/gfx/font_cache_thread.rs:639:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Script(1,1)' panicked at components/gfx/font_cache_thread.rs:639:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Script(1,1)' panicked at components/gfx/font_cache_thread.rs:639:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Style#1' panicked at components/gfx/font_cache_thread.rs:613:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Style#2' panicked at components/gfx/font_cache_thread.rs:639:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Script(1,1)' panicked at components/gfx/font_cache_thread.rs:613:14:
failed to send message to font cache thread: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread '<unnamed>' panicked at components/gfx/font_cache_thread.rs:371:59:
called `Result::unwrap()` on an `Err` value: Io(Custom { kind: BrokenPipe, error: "crossbeam-channel receiver closed" })
thread 'Constellation' panicked at components/constellation/constellation.rs:1231:21:
Unexpected script channel panic in constellation: RecvError
thread 'StorageManager' panicked at components/net/storage_thread.rs:61:36:
called `Result::unwrap()` on an `Err` value: Disconnected
thread 'ResourceManager' panicked at components/net/resource_thread.rs:229:45:
called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "Other crossbeam-channel error" } ```
@Gae24 Gae24 added the C-untriaged New issues that haven't been triaged yet label Apr 26, 2024
@mukilan
Copy link
Member

mukilan commented Apr 27, 2024

I'm not able to observe this issue on my Android device, with a build from latest master.

Could you please provide more information about the issue such as:

  1. Whether this is on an emulator or a real device?
  2. Version of Android running on the device/emulator.
  3. Architecture of the device/emulator (arm or intel, 32 bit or 64 bit).
  4. Steps to reproduce the issue: Is this intermittent? or consistently reproducible? Did you have to load a different page than the default servo.org page?

@Gae24
Copy link
Contributor Author

Gae24 commented Apr 27, 2024

I'm testing on a Samsung A52s with the armv7 build, happens always the servo page is not rendered correctly https://ibb.co/gdhsfBM

@mukilan mukilan added P-android Android devices and removed C-untriaged New issues that haven't been triaged yet labels Apr 29, 2024
mukilan added a commit to mukilan/servo that referenced this issue May 16, 2024
This is a speculative fix for servo#32161. A similar failure is
reproducible on the Android x86_64 emulator with API 35
system image. The fix has not been validated on the actual
device so potentially there might be other issues that need
to be fixed to complete servo#32161.

Signed-off-by: Mukilan Thiyagarajan <mukilan@igalia.com>
github-merge-queue bot pushed a commit that referenced this issue May 17, 2024
This is a speculative fix for #32161. A similar failure is
reproducible on the Android x86_64 emulator with API 35
system image. The fix has not been validated on the actual
device so potentially there might be other issues that need
to be fixed to complete #32161.

Signed-off-by: Mukilan Thiyagarajan <mukilan@igalia.com>
@mukilan
Copy link
Member

mukilan commented May 20, 2024

@Gae24 In theory, the changes in #32298 should have fixed this issue, but I couldn't validate reproduce this on my device so it would be great if you could confirm if the issue is fixed on your device after #32298.

@Gae24
Copy link
Contributor Author

Gae24 commented May 20, 2024

Can confirm the issue is fixed

@mukilan
Copy link
Member

mukilan commented May 21, 2024

Thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-android Android devices
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants