587589 - Tab scrolling arrows appear after opening Firefox (with app tabs?) [caused by Firebug]

Status: RESOLVED INVALID

(Firefox :: Extension Compatibility, defect)

Description

[Josh Tumath]

User-Agent:       Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3) Gecko/20100805 Firefox/4.0b3
Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3) Gecko/20100805 Firefox/4.0b3

This occurs on both beta 3 and the trunk.

Reproducible: Always

Steps to Reproduce:
1. Create some app tabs (if you haven't all ready).
2. Close Firefox.
3. When the message appears asking if you want to save your tabs, click on "Save and Quit".
4. Open Firefox again.
Actual Results:  
The tab scolling arrows appear (see screenshot).

Expected Results:  
They shouldn't have appeared.

Comment 1

[Josh Tumath]

Attachment: Screenshot of the bug

Notice how the "new tab" button has been moved as well.

Comment 2

[Josh Tumath]

Now I'm not entirely sure that this bug relates to app tabs, because it also happened without any app tabs when I opened Minefield.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Could you please run a test in a fresh profile? http://support.mozilla.com/en-US/kb/Managing+profiles

Comment 4

[Josh Tumath]

I tried that just now and the problem didn't occur.

In the past, I've noticed that this sometimes happens without any app tabs, so this probably has nothing to do with them.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

So lets investigate. Can you please move away your sessionstore.js file from within the affected profile while Firefox is not running? Can you repro the issue afterward?

Comment 6

[Josh Tumath]

Problem solved! Would you like me to attach the file to this bug?

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

First please trim down the file because it can contain sensitive data. When you open about:config in the location bar please search for:

browser.sessionstore.max_tabs_undo
browser.sessionstore.max_windows_undo

Set max_windows_undo to 1 so only sessions for the current window will be saved. Then decrease the number for max_tabs_undo until the problem goes away. Always do a backup between those steps while Firefox is closed.

Otherwise use an editor to rename visited websites from the js file.

Comment 8

[Josh Tumath]

Now the problem has started appearing again with the new sessionstore.js that Firefox created once I removed the old sessionstore.js.

(In reply to comment #7)
> First please trim down the file because it can contain sensitive data. When you
> open about:config in the location bar please search for:
> 
> browser.sessionstore.max_tabs_undo
> browser.sessionstore.max_windows_undo
> 
> Set max_windows_undo to 1 so only sessions for the current window will be
> saved. Then decrease the number for max_tabs_undo until the problem goes away.
> Always do a backup between those steps while Firefox is closed.
I'll do that now for you.

Comment 9

[Josh Tumath]

Oh, and by the way, there's one more thing I've found that seems to temporarily fix the problem (until it happens again), which is by creating new tabs until there are so many that the scrolling arrows are meant to appear anyway. Then, when I close them, the scrolling arrows disappear.

Comment 10

[Josh Tumath]

Actually, the js file is very big, and since all the data is all on one line, my text editor can't contain it all, so it would be very difficult for me to edit the file, or know what I'm doing. I don't think there's anything private in it, but, I don't want to attach the file, just in case there is.

Is it possible for me to send the file to you via email, Henrik?

Comment 11

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Yes, please send it to my gmail address. Thanks.

Comment 12

[Josh Tumath]

It seems that the problem had been caused by Test Pilot 1.0.1, which I had installed instead of the Feedback extension. When I removed Test Pilot, the Feedback extension came back, and I didn't see the problem occur again.

However, I couldn't reproduce the problem on a fresh new profile.

Comment 13

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to comment #12)
> It seems that the problem had been caused by Test Pilot 1.0.1, which I had
> installed instead of the Feedback extension. When I removed Test Pilot, the
> Feedback extension came back, and I didn't see the problem occur again.

Aakash, have you heard about such a problem before? IMO we should blame the test pilot extension and close the bug as invalid.

Comment 14

[Josh Tumath]

Actually, it seems that I'm wrong. This problem isn't being caused by test pilot addons; it's got nothing to do with them! Sorry about that.

The problem has been occuring, still, but it's been happening less. It happens when I switch builds from a Firefox beta to Minefield.

Comment 16

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to comment #14) 
> The problem has been occuring, still, but it's been happening less. It happens
> when I switch builds from a Firefox beta to Minefield.

Would be great to get the steps you have to do in a beta before restarting the browser.

Comment 17

[Josh Tumath]

It's good to know that I'm not the only one experiencing this bug.

Anyway, these are the steps that I take:
1. I click on the X button in the title bar to close the Firefox beta.
2. When the message appears asking if I want to save my tabs, I click on "Save and Quit".
3. I wait for a while for the firefox.exe process to close.
4. I open Minefield.

Comment 18

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Josh, which beta version are you using? Is it beta 6? Can you please start with a fresh session and give steps how you create tabs and the app tab. Eventually the exact order is necessary.

Comment 19

[Josh Tumath]

Yes, beta 6. I haven't been able to reproduce the problem, since it doesn't always occur. These are the steps that might reproduce the problem:

1. Open Firefox.
2. Go to http://mail.live.com and make it an App Tab.
3. Open a new tab and go to http://www.google.com (so that I can use it for iGoogle) and make it an App Tab.
4. Open two other tabs and go to any websites.
5. Click on the X button in the title bar to close Firefox.
6. Click on "Save and Quit".
7. Open Minefield.

I think it only occurs when I've had a long session, but I can't confirm that.

Comment 20

[Josh Tumath]

If anyone else who's following this bug is experiencing this issue, do you know how to reproduce this?

Comment 21

[cplarosa]

It seems to happen very randomly for me, but, more often than not, there are scroll arrows on the tab bar when I open Firefox 4 beta 6.  I have it configured to show my homepage when Firefox opens, so it's strange there are frequently scroll bars when there's only one tab open at startup.  In my case, there's no app tab opened -- just a normal tab.  Earlier today, I reopened Firefox several times in a row to try to get rid of the scroll bars, and they just wouldn't go away.  Now, later in the afternoon, it's working fine with no scroll bars when I start up.  I can't see a pattern so far.  It seems like an uninitialized variable or something like that.  The only extension I have installed is Firebug 1.6X.0b1.

Comment 22

[Wyatt Childers]

For me this happens even without app tabs. I think this shouldn't be linked to a app tab bug.

Comment 23

[cplarosa]

I just did a simple test:  I opened and closed Firefox 20 times in a row to see if the arrows would appear.  Here are the results:

10010011001000100011

Each digit above represents one open/close cycle of Firefox, where 1 = scroll arrows appear, and 0 = scroll arrows do not appear.

I am running Firefox 4.0b6 (32 bit) under Windows 7 Professional 64 bit with Firebug 1.6X.0b1 installed as the only extension (other than Feedback 1.0.3).  Firefox is configured to display a homepage in the local filesystem on startup.

I then disabled the Firebug extension and repeated the above 20 open/close cycles.  With Firebug disabled, the scroll arrows never appeared in 20 iterations.

So this may be a Firebug issue or a general extensions issue, a race condition of some sort, or uninitialized memory.  I'm not sure if other people who've seen this are using Firebug or other extensions.

Comment 24

[cplarosa]

I submitted this to Firebug and referenced this bug #:
  http://code.google.com/p/fbug/issues/detail?id=3442

Comment 25

[Josh Tumath]

For what it's worth, this problem has only ever occurred with Firebug enabled. I must have forgotten to disable it when investigating the issue.

Comment 26

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Thanks to both of you for investigation and confirmation! That is really helpful information. Great to see a bug filed on Firebug. Marking this bug as invalid based on the extension is the culprit.