Firefox crashes on fresh L4T 24.2, Ubuntu 16.04 LTS / aarch64

UNCONFIRMED
Unassigned

Status

()

Core
Widget: Gtk
P4
critical
UNCONFIRMED
2 years ago
a year ago

People

(Reporter: hmf, Unassigned)

Tracking

({crash})

48 Branch
ARM
Linux
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: tpi:-)

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160823121617

Steps to reproduce:

Install JetPack-L4T-2.3-linux-x64.run via Ubuntu 14.04 host on Jetson TX1, with OS flashed - without errors

Install Firefox using "sudo apt-get install firefox-dbg" -> version 48.0+build2-0ubuntu0.16.04.1 installed

Start Firefox in safe mode without plugins
Visit any site, click somewhere into content, follow some links - Boom!


Actual results:

Firefox disappears with a segmentation fault

<terminal output>

ubuntu@tegra-ubuntu:/usr/bin$ ./firefox

(firefox:3080): LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): GLib-CRITICAL **: g_find_program_in_path: assertion 'program != NULL' failed

(firefox:3080): GLib-CRITICAL **: g_find_program_in_path: assertion 'program != NULL' failed
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
get_inPrivateContext@chrome://global/content/bindings/autocomplete.xml:161:8
handleEnter@chrome://global/content/bindings/autocomplete.xml:540:18
handleKeyPress@chrome://global/content/bindings/autocomplete.xml:504:24
onKeyPress@chrome://global/content/bindings/autocomplete.xml:433:18
onxblkeypress@chrome://global/content/bindings/autocomplete.xml:617:8

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed

(firefox:3080): Gtk-CRITICAL **: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed
Segmentation fault
ubuntu@tegra-ubuntu:/usr/bin$ 
ubuntu@tegra-ubuntu:/usr/bin$ head -n 1 /etc/nv_tegra_release
# R24 (release), REVISION: 2.0, GCID: 7691362, BOARD: t210ref, EABI: aarch64, DATE: Thu Sep  8 20:59:21 UTC 2016


Expected results:

No crash at all

Updated

2 years ago
Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Updated

2 years ago
Severity: normal → critical
Keywords: crash
OS: Unspecified → Linux
Hardware: Unspecified → x86_64

Updated

2 years ago
Whiteboard: tpi:-

Updated

2 years ago
Priority: -- → P4
This is on Linux/aarch64, not x86_64.
Hardware: x86_64 → ARM
Summary: Firefox crashes on fresh L4T 24.2, Ubuntu 16.04 LTS → Firefox crashes on fresh L4T 24.2, Ubuntu 16.04 LTS / aarch64
hmf, could you file a bug to your distribution?  Because Mozilla doesn't provide built binary for Linux/aarch64.

If you point out more detail into our source code, we can fix this.
(Reporter)

Comment 3

2 years ago
(In reply to Makoto Kato [:m_kato] from comment #2)
> hmf, could you file a bug to your distribution?  Because Mozilla doesn't
> provide built binary for Linux/aarch64.
> 
> If you point out more detail into our source code, we can fix this.

Yep, I have forwarded it to the JetPack team.

Updated

2 years ago
See Also: → bug 1302554
You need to log in before you can comment on or make changes to this bug.