Closed Bug 1611787 Opened 5 years ago Closed 2 years ago

Crash on startup on WSL

Categories

(Core :: Widget: Gtk, defect)

73 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: revitale76, Unassigned)

Details

(Keywords: regressionwindow-wanted)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

run "firefox" command on WSL

uname -a:
Linux 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

Actual results:

Got the following message:

Exiting due to channel error.

###!!! [Parent][MessageChannel] Error: (msgtype=0x1E0059,name=PBrowser::Msg_UpdateEffects) Channel error: cannot send/recv

Expected results:

firefox start normally.

Hi, Thanks for taking the time to report this issue, unfortunately this issue requires an WSL installation on our windows 10 machines and our environment is not set up for that, I will set the component for this issue and maybe one of our developers can take a look and might be able to reproduce it on their end.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

If Firefox ESR works using MozRegression would be helpful to track down what is the regressing issue for this setup. Given the nonstandard nature of the setup someone who wants this to work would be a great help here.

QA Whiteboard: [qa-regression-triage]

@revitale76@gmail.com: Can you help us investigate this?

  1. For starters, as mentioned in comment 2, it would be very important to know if it still reproduces. And in which version.
  2. Then determine if it reproduces in ESR version of Firefox (v91.13.0esr).
  3. If it reproduces in the more recent versions and it does not in ESR, then it means it may be a regression and could be investigated using the mozregression application to find out when it was introduced.

I'll try to guide you through the investigation if we get to it. This is quite an old bug that may not still reproduce.

Thank you for your contribution!

Flags: needinfo?(revitale76)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(revitale76) → needinfo?(stransky)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(stransky)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.