Closed Bug 1546006 Opened 6 years ago Closed 5 years ago

FF Nightly closes Oracle VM VirtualBox and my Ubuntu 18.04 session when failing to exit

Categories

(Core :: Widget: Gtk, defect, P5)

68 Branch
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: jeando.veuve, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

I tried to close FF Nightly 68.0a1 (2019-04-20) (64 bits) running on an Ubuntu 19.04 (2019-04-20) VM in Oracle VM VirtualBox Version 5.2.18 r124319 (Qt5.9.5).

Problems happen regularly, but not always, after a long session (more than 3 hours) on imgur.com.
Happened also with various beta versions of Ubuntu 19.04 and previous versions of Nightly.

It's a brand new installation I started to test Nightly & Ubu 19.04. I don't have older versions of Nightly on this.

Problem doesn't happen with FF standard version.
Problem doesn't happen with Ubuntu 18.04 LTS and Nightly I use as my main OS/Browser on an everyday base.

Form now on, I will run Nightly on my VM Ubuntu 18.10 to see if the same problem occurs and report it here

Actual results:

When failing to exit properly, FF Nightly closed brutally my VM in Oracle VM VirtualBox AND my session in my Ubuntu 18.04 LTS that runs the whole.

Expected results:

Nighlty should have closed nicely its tab and/or its session leaving me with a running 19.04 VM atop my Ubuntu 18.04 session.

The Virtual Machines run atop an Ubuntu 18.04 LTS

Summary: FF Nightly closes Oracle VM VirtualBox and my Ubuntu 19.04 session when failing to exit → FF Nightly closes Oracle VM VirtualBox and my Ubuntu 18.04 session when failing to exit

Hi Jean-Do,

Thank you for your report. Giving the fact that we don't have the proper environment I'm not sure if I'll be able to test it on my end.
I'll set the component to Core:Widget: GTK, I think this is a good starting point.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Priority: -- → P5

New version of FF Nightly resolves the problem

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.