chromium from terminal sometimes hangs

Open
#3,304 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, raspberry-pi

Research direction

The report names /usr/bin/xdg-open, Chromium, and the Raspberry Pi system details but no kernel file or test. First verify whether the issue belongs in this kernel repository, then reproduce repeated URL launches and compare the reported Chromium, DBus, and VSync messages. Done would require identifying the affected component and a defined fix or handoff.

Written by the indexing model from the issue text.

Description

Is this the right place for my bug report?
Eben Upton told me to create it here, even though it’s “not really the appropriate repo, but it will do”

Describe the bug
Bad things happen using /usr/bin/xdg-open to open urls in Chromium. Sometimes it works fine, sometimes Chromium freezes up, sometimes the whole desktop environment freezes up tens of seconds. Once I had to pull the plug because after minutes it didn’t come back.

To reproduce
Open a terminal and run this command several times:
/usr/bin/xdg-open "https://support.speedify.com/"

Expected behaviour
If the browser’s not running, it should start on the URL, if it’s not it should quickly open another tab to that URL.

Actual behaviour
Most times it works, but sometimes, it takes a very long time and the browser or even the whole desktop freeze up while it’s waiting.

Here I ran it a couple times. See the large “ERROR:browser_process_sub_thread.cc(217)] Waited 678 ms for network service” type messages. Ive seen them go above 3000 and that’s when things get really hung up (for much longer than the 3 seconds you’d think from the message)

And sometimes when it has to launch chromium, it does, but the command never returns at all. I added some <> inline:

pi@raspberrypi:~ $ /usr/bin/xdg-open "https://support.speedify.com/"
 --disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
Opening in existing browser session.
[10190:10217:1028/110147.338737:ERROR:browser_process_sub_thread.cc(217)] Waited 678 ms for network service
pi@raspberrypi:~ $ /usr/bin/xdg-open "https://support.speedify.com/"
 --disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
Opening in existing browser session.
[10400:10427:1028/110209.251330:ERROR:browser_process_sub_thread.cc(217)] Waited 1020 ms for network service
pi@raspberrypi:~ $ /usr/bin/xdg-open "https://support.speedify.com/"
 --disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
Opening in existing browser session.
[10608:10635:1028/110220.586378:ERROR:browser_process_sub_thread.cc(217)] Waited 1324 ms for network service
<< COMMENT ADDED AFTER:  CHROMIUM CRASHES HERE >>
pi@raspberrypi:~ $ /usr/bin/xdg-open "https://support.speedify.com/"
 --disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
[10817:10962:1028/110252.280961:ERROR:object_proxy.cc(619)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
[10866:10866:1028/110254.269346:ERROR:gl_surface_presentation_helper.cc(244)] GetVSyncParametersIfAvailable() failed for 1 times!
[10866:10866:1028/110254.277883:ERROR:gl_surface_presentation_helper.cc(244)] GetVSyncParametersIfAvailable() failed for 2 times!
^C[10817:10845:1028/110323.523693:ERROR:browser_process_sub_thread.cc(217)] Waited 15 this ms for network service
<< COMMENT ADDED AFTER: CHROMIUM LAUNCHED AND SHOWED URL, BUT  THIS COMMAND NEVER RETURNED.  WHEN I FINALLY HIT CTRL-C CHROMIUM WENT AWAY>>

System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:

  • Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
    4B

  • Which OS and version (cat /etc/rpi-issue)?
    Raspberry Pi reference 2019-09-26
    Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 80d486687ea77d31fc3fc13cf3a2f8b464e129be, stage5

  • Which firmware version (vcgencmd version)?
    Sep 24 2019 17:34:30
    Copyright (c) 2012 Broadcom
    version cd3add54955f8fa065b414d8fc07c525e7ddffc8 (clean) (release) (start)

  • Which kernel version (uname -a)?
    Linux raspberrypi 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux

Logs
If applicable, add the relevant output from dmesg or similar.

Additional context
Add any other relevant context for the problem.

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.