Closed
Bug 813563
Opened 13 years ago
Closed 12 years ago
Firefox process doesn't close with bug 813572 (Conduit toolbars)
Categories
(WebExtensions :: General, defect)
Tracking
(firefox17-)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox17 | - | --- |
People
(Reporter: mihaelav, Unassigned)
References
Details
(4 keywords, Whiteboard: [STR:comment 4])
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 RCbuild2
Having Yandex Community Toolbar3.15.1.0 or Hotspot Shield Community Toolbar3.15.1.0 add-on installed, "Restore Previous Session" button is removed from about:home page and from History menu
Reproducible: always (about 10 tries)
Steps:
1. Install Yandex Community Toolbar3.15.1.0 or Hotspot Shield Community Toolbar3.15.1.0 add-on
(http://ct57527.ourtoolbar.com/, http://hotspotshield.ourtoolbar.com/)
2. Open a few tabs (pinned tabs, as well)
3. Make sure "Show my home page" is selected for startup in Options
4. Close Firefox
5. Start firefox
Expected result: about:home page is displayed (and pinned tabs) containing the restore previus session button. "Restore Previous Session" option is enabled unde History menu
Actual result: about:home page is displayed (and pinned tabs) but restore previous button is not visible. "Restore Previous Session" option is disabled in History menu.
Reproducible also on Firefox 16.0.2
Does this only reproduce on Linux? What about Firefox versions before 16.0.2?
| Reporter | ||
Comment 2•13 years ago
|
||
On thorough investigation, the problem is caused by Firefox process still running after Firefox is closed (so it cannot restore "previous" session since it runs in the same session).
Also, I cannot reproduce the issue constantly anymore (it is intermittent).
Summary: Cannot restore previous session (with Yandex Community Toolbar3.15.1.0 and Hotspot Shield Community Toolbar3.15.1.0) → Firefox process doesn't always close (with Yandex Community Toolbar3.15.1.0 and Hotspot Shield Community Toolbar3.15.1.0)
Mihaela, please try to find out a reproducible test for this bug. Dataloss is a serious issue.
Keywords: dataloss,
steps-wanted
| Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #3)
> Mihaela, please try to find out a reproducible test for this bug. Dataloss
> is a serious issue.
I reproduced again the process hanging after closing firefox, using the following steps:
1. Start firefox with a new profile
2. In stall 4shared.com toolbar (http://downloadmytoolbar.com/4shared/LP/download.html)
3. Restart firefox
4. Try to open some new tabs (quickly clicking on the new tab button - "+")
-> bug #813572 occurs
5. Close firefox from the "X" button
6. Check if firefox process is closed (ps -e | grep firefox)
Actual result: Process is still running
So this isn't just Yandex and Hotspot then, it's probably all Conduit-based toolbars.
Summary: Firefox process doesn't always close (with Yandex Community Toolbar3.15.1.0 and Hotspot Shield Community Toolbar3.15.1.0) → Firefox process doesn't close with bug 813572 (Conduit toolbars)
Keywords: steps-wanted → reproducible
Whiteboard: [STR:comment 4]
I can't reproduce this in Firefox 15.0, 16.0, 16.0.2.
I can reproduce this with Firefox 17.0. It would seem that if this is our regression, it started in Firefox 17. Now looking for a better regression range.
Last Good: 2012-08-18
First Bad: 2012-08-19
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=812ea773f166&tochange=8c85c83068e7
Mihaela, please work on the mozilla-inbound builds to see if you can regress this further.
Alex, I'm nominating this for tracking as it appears to be a Firefox 17 regression in relation to Conduit toolbars.
tracking-firefox17:
--- → ?
Keywords: regression
Comment 8•13 years ago
|
||
Hi,
My name is Shiran and I'm from the support team in Conduit.
Just to clear something, are we talking only on Linux OS?
Comment 9•13 years ago
|
||
We've reached out to developers on the Conduit side, looks like this should be a fix on their side at this point, renom if that changes after investigation by extension devs.
| Reporter | ||
Comment 10•12 years ago
|
||
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #7)
> Last Good: 2012-08-18
> First Bad: 2012-08-19
>
> Pushlog:
> http://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=812ea773f166&tochange=8c85c83068e7
>
> Mihaela, please work on the mozilla-inbound builds to see if you can regress
> this further.
>
> Alex, I'm nominating this for tracking as it appears to be a Firefox 17
> regression in relation to Conduit toolbars.
I could not reproduce on inbound with the provided pushlog (by locally bisecting and building firefox). I could not reproduce on August 19 Nightly, either
Comment 11•12 years ago
|
||
(In reply to Mihaela Velimiroviciu [QA] (:mihaela) from comment #10)
> I could not reproduce on inbound with the provided pushlog (by locally
> bisecting and building firefox). I could not reproduce on August 19 Nightly,
> either
I don't understand. That means your regression range is wrong and you can't reproduce this anymore at all?
Comment 12•12 years ago
|
||
Hi
Please let me know if the issue still reproduced
Comment 13•12 years ago
|
||
Mihaela, please find reliable steps to reproduce this bug. If you can't, reproduce this anymore, resolve WORKSFORME.
Keywords: verifyme
QA Contact: mihaela.velimiroviciu
| Reporter | ||
Comment 14•12 years ago
|
||
The toolbars' version available at the provided links has changed to 3.16.0.3, so I guess that's why I cannot reproduce anymore, even with the build from bug description.
Marking WORKSFORME for now.
| Assignee | ||
Updated•6 years ago
|
Component: Add-ons → General
Product: Tech Evangelism → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•