What controls the Firefox 38/39 border size & default page zoom level?

[Karlheinz Fenstermacher]

In another thread, we proved the existence of an unknown-as-yet bug
in Firefox 38 (Canonical distribution) & Firefox 39 (Mozilla
distribution) which I am trying to determine what the cause is.

A key unanswered question is:

What controls the Firefox 38/39 border size & default page zoom level,
and, did that change between Firefox 37 and 38?

[Caver1]

If you discovered a bug did you report it?

--
Caver1

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 11:20:08 -0400, Caver1 wrote:

> If you discovered a bug did you report it?

Yes. I reported it here, in this newsgroup. Gory details are in
another thread of a few days ago (which, of course, you
participated in so you knew that).

I don't have enough data to JUSTIFY filing the bug report
yet, and you knew that also.

Not everyone is seeing the bug that I see, and you knew that
also.

So, as in many bugs, it doesn't happen to everyone (which you
knew).

Since it doesn't happen to everyone, there is *always* the
chance that it is system specific (and you knew that too).

Since it *could* be system specific, I would not yet file the
report until I can isolate it down to something that is
simpler than shipping my entire system to the Mozilla developers
for *them* to isolate the root cause (clearly you know this).

What I need to ISOLATE the root cause, is to understand *WHERE*
to look.

Hence the valid and legitimate question:

What controls the Firefox 38/39 border size & default page

zoom level,and, did that change between Firefox 37 and 38?

[WaltS48]

On 07/05/2015 12:01 PM, Karlheinz Fenstermacher wrote:
> On Sun, 05 Jul 2015 11:20:08 -0400, Caver1 wrote:
>
>> If you discovered a bug did you report it?
>
> Yes. I reported it here, in this newsgroup. Gory details are in
> another thread of a few days ago (which, of course, you
> participated in so you knew that).

We are not Firefox developers. Report it here.

[Enter A Bug](https://bugzilla.mozilla.org/enter_bug.cgi)

Follow the guidelines. [Bug writing guidelines - Mozilla |
MDN](https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines)


--
Kubuntu 14.10 | KDE 4.14.1 | Thunderbird 42.0a1(Daily) Go Bucs!
[Coexist · Understanding Across Divides](https://www.coexist.org/)
[Visit Pittsburgh](http://www.visitpittsburgh.com)
[Deutschtown Music Festival | A free full day of music July 11th,
featuring 120+ live bands playing all over
Deutschtown](http://deutschtownmusicfestival.org/)

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 12:09:38 -0400, WaltS48 wrote:

> We are not Firefox developers. Report it here.

> https://bugzilla.mozilla.org/enter_bug.cgi

I will have to say that the bug is not fleshed out well
enough to report yet.

It still *could* be something on my system, for example.
Or, it could be a design decision, for example, by Canonical.

I don't know this yet, and to know more, I need to ISOLATE what
the root cause is.

I didn't know you guys aren't developers, as I would have thought
developers reside on a support newsgroup though.

[Caver1]

On 07/05/2015 12:01 PM, Karlheinz Fenstermacher wrote:

> On Sun, 05 Jul 2015 11:20:08 -0400, Caver1 wrote:
>
>> If you discovered a bug did you report it?
>
> Yes. I reported it here, in this newsgroup. Gory details are in
> another thread of a few days ago (which, of course, you
> participated in so you knew that).

Reporting it here does no good if it is a bug which I doubt.

--
Caver1

[Ron K.]

Zooming increment values are set by a preference in prefs.js editable with
about:config.

User Interface borders a function of the theme.

--
Ron K.
Who is General Failure, and why is he searching my HDD?
Kernel Restore reported Major Error used BSOD to msg the enemy!

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 15:59:21 -0400, Caver1 wrote:

> Reporting it here does no good if it is a bug which I doubt.

Well, both work in the same direction, because if it's not
a bug, then reporting it would do no good (and would actually
waste the developers' time).

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 15:32:05 -0500, Ron K. wrote:

> Zooming increment values are set by a preference in prefs.js
> editable with about:config.
> User Interface borders a function of the theme.

THANK YOU!

That's a good answer that the about:config must contain the default
zoom level, and that the "theme" (whatever that means) must set
the border sizes.

Both suggestions appear to have worthwhile merit in initial tests.

Starting with the THEME, I downloaded the suggested Classic Theme
Restorer, version 1.3.4, and it did *change* the look of the
border, although it was still huge (just less so) by default.

https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/

However, with button presses, I found I could SHRINK the border
which is proving that the only reason others don't see what I'm
seeing is that they never optimized their borders in the first
place.

So, I'm realizing, belatedly, the reason others don't see any
change between Firefox 37 and 38 is that they never optimized
either one (and, apparently, none are using Tor Browser Bundle,
which is already optimized).

So, what that tells me is that the default THEME likely changed
between Firefox 37 and 38, but the only ones who notice it are
those who were efficient in Firefox 37 in the first place.

Regarding the default zoom level, since there is no $HOME/.mozilla
directory when I start Firefox in these tests, there can't be any
overide of settings in user.js.

However, looking in about:config for the word "zoom", there are
potential settings which may affect the default zoom level:

apz.zoom_animation_duration_ms;250
browser.gesture.tap;cmd_fullZoomReset
browser.panorama.animate_zoom;true
browser.zoom.full;true
browser.zoom.reflowOnZoom;false
browser.zoom.reflowZoom.reflowTextOnPageLoad;true
browser.zoom.reflowZoom.reflowTimeout;500
browser.zoom.siteSpecific;true
browser.zoom.updateBackgroundTabs;true
devtools.eyedropper.zoom;6
devtools.toolbox.zoomValue;1
devtools.webide.zoom;1
layers.async-pan-zoom.enabled;false
pdfjs.defaultZoomValue;
pdfjs.useOnlyCssZoom;false
toolkit.zoomManager.zoomValues;.3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
zoom.maxPercent;300
zoom.minPercent;30

Any suggestion as to which 'zoom' setting is the one that would
start about three "clicks" (of ctrl + -) zoomed out further than
these defaults?

[Ron K.]

This is the zoom pref I was thinking about:
toolkit.zoomManager.zoomValues;.3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
You seem to understand using a user.js file to force loading your pref
revisions at startup.
devtools.toolbox.zoomValue;1 may be what sets zoom to 100 percent at start.

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 02:14:21 -0500, Ron K. wrote:

> This is the zoom pref I was thinking about:
> toolkit.zoomManager.zoomValues;.3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
> You seem to understand using a user.js file to force loading your pref
> revisions at startup.
> devtools.toolbox.zoomValue;1 may be what sets zoom to 100 percent at start.

Thanks for the suggestion.

I did play with the toolkit.zoomManager.zoomValues by making them equal to
1,2,3,4 but (AFAICT) all that did was define what each "Control minus" or
"Control Plus" keystroke jumped to.

I have no problem using a user.js file; the problem is what settings to
use for the zoom level, so, I'll try that devtools.toolbox.zoomValue
setting in a moment.

Here is the best I can get the Firefox 39 to be compact in the up:down
direction, by the way, using Classic Theme Restorer:

http://i.imgur.com/7Y8uCNL.jpg

Firefox 39 wasted space is still way huger than it was (as compared with
TBB on the right); but at least it's smaller than the atrocious THEME
that Mozilla supplies by default ever since FF38.

[Karlheinz Fenstermacher]

> I have no problem using a user.js file; the problem is what settings to
> use for the zoom level, so, I'll try that devtools.toolbox.zoomValue
> setting in a moment.

First, I tried this:
devtools.toolbox.zoomValue;100

Then I tried 10,and then .5, but it didn't seem to do anything (yes,
I closed and restarted Firefox in between).

So, the default zoom level must be set elsewhere...

[WaltS48]

On 07/06/2015 01:42 AM, Karlheinz Fenstermacher wrote:
> On Sun, 05 Jul 2015 15:32:05 -0500, Ron K. wrote:
>
>> Zooming increment values are set by a preference in prefs.js
>> editable with about:config.
>> User Interface borders a function of the theme.
>
> THANK YOU!
>
> That's a good answer that the about:config must contain the default
> zoom level, and that the "theme" (whatever that means) must set
> the border sizes.
>
> Both suggestions appear to have worthwhile merit in initial tests.
>
> Starting with the THEME, I downloaded the suggested Classic Theme
> Restorer, version 1.3.4, and it did *change* the look of the
> border, although it was still huge (just less so) by default.
>
> https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/
>
> However, with button presses, I found I could SHRINK the border
> which is proving that the only reason others don't see what I'm
> seeing is that they never optimized their borders in the first
> place.
>

Nothing to optimize for me.

The borders you keep going on about are actually the space between 3
components of the Window. From the top Window Title Bar, Firefox Tab bar
and the Firefox Address Bar.

> So, I'm realizing, belatedly, the reason others don't see any
> change between Firefox 37 and 38 is that they never optimized
> either one (and, apparently, none are using Tor Browser Bundle,
> which is already optimized).
>
> So, what that tells me is that the default THEME likely changed
> between Firefox 37 and 38, but the only ones who notice it are
> those who were efficient in Firefox 37 in the first place.

The default theme didn't change.

Here is a screen shot of Firefox 29.0-the first Firefox with the
Australis theme-and Firefox 36.0.4, matched up against 38.0.

http://imgur.com/2I24xea

I don't recall noticing a difference in the Tab bar or Address bar size
in 37.0, don't know why they would shrink it, then set it back to the
original size of Firefox 29.0 in Firefox 38.0.

>
> Regarding the default zoom level, since there is no $HOME/.mozilla
> directory when I start Firefox in these tests, there can't be any
> overide of settings in user.js.
>

Move the profiles to another location?

<snip useless information to me>

> Any suggestion as to which 'zoom' setting is the one that would
> start about three "clicks" (of ctrl + -) zoomed out further than
> these defaults?
>
>

Ctrl+0 resets Zoom to 100%

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 11:09:51 -0400, WaltS48 wrote:

> Move the profiles to another location?

Just to remind folks, I have been deleting $HOME/.mozilla on
every test, so, it can't possibly be my profiles.

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 11:09:51 -0400, WaltS48 wrote:

>> Any suggestion as to which 'zoom' setting is the one that would
>> start about three "clicks" (of ctrl + -) zoomed out further than
>> these defaults?
>
> Ctrl+0 resets Zoom to 100%

That would work if the 100% zoom wasn't already defined, by the
update from Firefox 37 to Firefox 38 differently.

As it is, control+0 does absolutly nothing because Firefox STARTS
at the 100% level, which, as we have noted, in the older Firefox
37 and in the firefox used by the TBB, is just fine, but in the
newer Firefox 38+, is three clicks too big.

I guess what you're really saying is that I should figure out
how to *change* the definition of the 100% zoom level to be
three clicks further zoomed out.

That would work. I will work on that, because, if I can change the
default zoom level definition in Firefox 38, it will work around
that bug beautifully, if I can figure out how to do it.

It probably has something to do with:
zoom.maxPercent;300
zoom.minPercent;30

So, I just tried this:
1. I removed $HOME/.mozilla
2. I started Firefox 38 and went to about:config
3. I set: zoom.maxPercent;100
4. I killed Firefox 38
5. I started Firefox 38
6. I went to any web page

Whoa! Kewl! The zoom level is BETTER! Muuuuuch better!
You were on to something!

So, I repeated with the max zoom percent set to 50%, and
went to a web page. I didn't measure, but it didn't seem to
be different (but it was still better than the original
settings in Firefox 38).

So, I think we have a workaround to the Firefox 38 zoom level
bug. Thank you very much for showing me the workaround!

NOTE: It *has* to be a bug in Firefox because on the exact
same system, the older firefox does *not* exhibit this problem,
and that's without any profile either.

[FoxWolfie Galen]

On Mon, 6 Jul 2015 02:14:21 -0500, "Ron K." <kil...@gisco.net> wrote:

> This is the zoom pref I was thinking about:
> toolkit.zoomManager.zoomValues;.3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
> You seem to understand using a user.js file to force loading your pref
> revisions at startup.
> devtools.toolbox.zoomValue;1 may be what sets zoom to 100 percent at start.

I don't think any of those about:config prefs you listed control the
"default" zoom level.

If you are only concerned with the zoom level on page content, then I think
the default is related to your chosen font size. Find the font settings and
try moving those up or down. This should work, assuming you change the
right font sizes. This won't affect Firefox's menus and interface. It just
affects the page content area. It also isn't 100 percent effective, unless
you turn off the option for pages to download their own fonts.

We can set the minimum font size, which is great, but I really wish we
could also set the maximum font size as well. Then, nothing could ever be
too small to read, nor so large that it requires horizontal scrolling to
the moon and back! People's two inch tall fonts on some eBay pages come to
mind.


If you are also concerned with the size of Firefox's menus and other parts
of the browser, going to about:config and changing this setting might help.

layout.css.dpi

It probably defaults to 1 or -1. Remember what it is before making a
change, as you might need to put it back. If you want stuff to appear
zoomed out about three levels, I think you could put .7 as the value. A
value of 2 would be twice the normal size for everything, and a value of .5
would be half the size for everything. This is supposed to affect the size
everything, menus, buttons and page content, so it might not be what you
want.

If you use a number that is too large or small, you could make the browser
interface unusable and not be able to change it back from within the
browser. In that case, you'd need to edit you prefs.js or user.js to
remove the setting, and it would return to default.

I just wish the developers would stop messing with usability defaults and
the interface every few versions. There's no good reason that users should
need to resort to add-ons like Classic Theme Restorer, just to fix things
that were never originally broken.

[WaltS48]

On 07/06/2015 01:49 PM, FoxWolfie Galen wrote:
> There's no good reason that users should
> need to resort to add-ons like Classic Theme Restorer, just to fix things
> that were never originally broken.

There's no good reason to resort to CTR at all.

[PietB]

WaltS48 wrote:
> There's no good reason to resort to CTR at all.

There is. Plenty of arguments have been given here and
in moz.general, so there's no use in repeating them.
I, for one, am glad that there is something like CTR.
And apparently some half million others think so too.

-p

[Caver1]

Where are the zoom levels set on the older Firefox? They should be they
defaults of 300 and 30.
The only problem I see with you changing the max zoom level is that you
won't be able to zoom in on anything if need be.
I don't know about you but my eyes are aging and need some help now and
again. :)

--
Caver1

[Caver1]

On 07/06/2015 02:03 PM, WaltS48 wrote:
> On 07/06/2015 01:49 PM, FoxWolfie Galen wrote:
>> There's no good reason that users should
>> need to resort to add-ons like Classic Theme Restorer, just to fix things
>> that were never originally broken.
>
>
> There's no good reason to resort to CTR at all.
>

There is if you don't like the looks. Everybody is different.

--
Caver1

[Dave Symes]

In article
<mailman.1623.143620585...@lists.mozilla.org>,

WaltS48 <thali...@EVOMERaim.com> wrote:
> On 07/06/2015 01:49 PM, FoxWolfie Galen wrote:
> > There's no good reason that users should need to resort to add-ons
> > like Classic Theme Restorer, just to fix things that were never
> > originally broken.


> There's no good reason to resort to CTR at all.

There is if you want Firefox in a usable form and not a Goggle Chrome
clone.

If it wasn't for CTR, I for one, among a lot of folks would have moved to
Pale Moon...

Dave

--

Dave Triffid

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 15:17:34 -0400, Caver1 wrote:

> Where are the zoom levels set on the older Firefox? They should be they
> defaults of 300 and 30.
> The only problem I see with you changing the max zoom level is that you
> won't be able to zoom in on anything if need be.
> I don't know about you but my eyes are aging and need some help now and
> again.

Caver1,

You and HASM (and a few select others) were the ones who were instrumental
in providing the two workarounds that (almost) ameliorate the two Firefox
38+ bugs that were discussed here, and for that, I thank you!

You're the best of the best, because the advice panned out, and was
logical, and stayed on topic (I'm sorry I was so frustrated, but I never
thought a simple update of Firefox would take days to recover from).

To answer your questions, if I open up the TBB Firefox and type
about:config, and then filter on "zoom", I find:

zoom.maxPercent;300
zoom.minPercent;30

So, you see, it has *nothing* to do with the operating system (per se),
but all to do with how Firefox 38+ interacts with (something) differently
than it did before.

If it matters, here are the other related settings of the "good" firefox:
toolkit.zoomManager.zoomValues;.3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
devtools.toolbox.zoomValue;1
devtools.eyedropper.zoom;6
browser.zoom.siteSpecific;false
browser.zoom.full;true

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 14:03:44 -0400, WaltS48 wrote:

> There's no good reason to resort to CTR at all.

Clearly, the bug exists only in Firefox 38+ in that I can put
an older Firefox side by side with Firefox 38+ and *only* the
newer Firefox will exhibit the two bugs discussed here:
1. The default initial zoom level is 3x too large, and,
2. The toolbar area is about 2x as large as it was before.

Luckily, and thankfully, this frustrating days-long ordeal is
almost over, because of two very simple workarounds:
1. Change "zoom.maxPercent" from 300 to 50, and,
2. Use Classic Theme Restorer to shrink the toolbar area.

Neither workaround is perfect, since there are side effects of
the first, and the second doesn't allow you to get to where you
were in space saving, but, it's a LOT better (which is going
to have to do, for now).

So, while I hate adding yet another extension to work around a
flaw in Firefox (anyone remember the browserclosebuttons fiasco?),
the CTR extension almost works around the problem.

So, thank you all very much, especially to WaltS48 & WaltS,
Q, Caver1, HASM, Wildman, Jonathan N. Little, EE, & John Corliss.

I'm pretty much done with this.

I had never expected something as mundane as a firefox update to
be so miserable, and, I'm sorry if I got frustrated when people
didn't understand (and sometimes I didn't understand things).

But, there's no doubt that the older Firefox works just fine
while the newer Firefox does not, and there's nothing *else*
that's different on the system because that happens at the
very same time with or without a profile directory.

Thank you all.
The two workarounds to the two bugs are the best we can do,
and that's OK because each one is almost a solution.

THANK YOU THANK YOU THANK YOU THANK YOU.

[Caver1]

On 07/06/2015 04:40 PM, Karlheinz Fenstermacher wrote:
> On Mon, 06 Jul 2015 14:03:44 -0400, WaltS48 wrote:
>
>> There's no good reason to resort to CTR at all.
>
> Clearly, the bug exists only in Firefox 38+ in that I can put
> an older Firefox side by side with Firefox 38+ and *only* the
> newer Firefox will exhibit the two bugs discussed here:
> 1. The default initial zoom level is 3x too large, and,
> 2. The toolbar area is about 2x as large as it was before.

Is anybody else seeing this?

--
Caver1

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 14:40:54 -0400, Caver1 wrote:

> It could be something else is conflicting with Firefox 38/39 on your
> system that is causing this and not Firefox's fault.

To be logical, I must agree.

1. Firefox 37 & below worked fine when in the most compact form possible.
2. Firefox 38 and up no longer can be as compact, even with CTR.
3. Side by side, the newer FF shows the problem while the older one does not.

Therefore, *something* is different between FF37 & FF38 since the
operating system is exactly the *same* in both cases.

Note: A better test for me would be to unpack a Canonical Firefox 37,
if I can find it (or even a Mozilla Firefox 37) because that would be
the best apples-to-apples test case possible.

[Caver1]

https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

--
Caver1

[WaltS48]

Here is a screen shot of Firefox 29.0-the first Firefox with the
Australis theme-and Firefox 36.0.4, matched up against 38.0.

Using a test user account and a different profile for each.

http://imgur.com/2I24xea

Not seeing it.

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 18:05:47 -0400, Caver1 wrote:

> https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

Thanks.
I found an original copy of Firefox 37.0.1 (and a few others)
on my system in my software download directory, so I tried that
first:

Starting with a previously saved copy of firefox-37.0.1.tar.bz2
$ tar xjf firefox-*.tar.bz2
$ killall firefox
$ rm -rf $HOME/.mozilla
$ ./firefox/firefox &
$ ./firefox
=> XPCOMGlueLoad error for file /mytmp/firefox_37.0.1/firefox/libxul.so:
=> libXcomposite.so.1: cannot open shared object file: No such file or directory
=> Couldn't load XPCOM.
$ $ locate libXcomposite.so.1
=> /usr/lib/x86_64-linux-gnu/libXcomposite.so.1
=> /usr/lib/x86_64-linux-gnu/libXcomposite.so.1.0.0

Then, I downloaded Firefox 37.0.2 from here:
https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
but it had the same problem.

I need to debug why it can't find the shared object module (probably
a path issue somewhere).

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 17:27:00 -0500, Karlheinz Fenstermacher wrote:

> I need to debug why it can't find the shared object module (probably
> a path issue somewhere).

I worked my way backward to a Firefox version that worked again
from the bz2 file, and succeeded with Firefox 35.0.1 finally.

$ ./firefox/firefox --version
=> (process:9577): GLib-CRITICAL **: g_slice_set_config:
assertion 'sys_page_size == 0' failed
Mozilla Firefox 35.0.1

$ rm -rf $HOME/.mozilla

$ killall firefox

$ ./firefox/firefox &

Bingo! Everything looks BEAUTIFUL! (For the first time in days!)
http://i.imgur.com/TiJkM5Y.jpg

Now it's time to bring up Firefox 39, but, up until now, I have
been comparing with the Tor Browser Bundle, which, AFAIK, does
not use $HOME/.mozilla. However, is FF39 is going to use the same
$HOME/.mozilla directory?

Anyway, I started up FF39 while FF35 was running:

$ cd /firefox39/
$ ./firefox/firefox &

Drat. It brought up the same Firefox? Huh?
http://i.imgur.com/fmyebkY.jpg

I need to figure out a way to run two firefoxes together, when
one isn't the Tor Browser Bundle (but I can already see that both
bugs are resolved with the older Firefox 35).

What's the trick to running two Firefox versions, side to side?

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 18:08:02 -0400, WaltS48 wrote:

> Here is a screen shot of Firefox 29.0-the first Firefox with the
> Australis theme-and Firefox 36.0.4, matched up against 38.0.
>
> Using a test user account and a different profile for each.
>
> http://imgur.com/2I24xea
>
> Not seeing it.

Using the *same* user, same system, removed ~/.mozilla directory,
look at this comparison of Firefox 39 at the left and Firefox 35
at the right on the same screen, just moments apart.

I left the side panel on so you can see I didn't mess with the size:
http://i.imgur.com/h63JydT.jpg

If that doesn't show the bug extremely clearly, the only other
thing I can do is run them *both* at exactly the same time, but,
I don't know how to do that.

But, even so, they were run seconds apart, so, there's *nothing*
in my system that changed in the interim.

Now, the question is why do "I" very consistently and extremely
clearly see the problem, yet, none of you see it?

$ uname -a
=> Linux xyz 3.13.0-48-generic ... x86_64 GNU/Linux

[Karlheinz Fenstermacher]

>> Here is a screen shot of Firefox 29.0-the first Firefox with the
>> Australis theme-and Firefox 36.0.4, matched up against 38.0.
>>
>> Using a test user account and a different profile for each.
>>
>> http://imgur.com/2I24xea
>>
>> Not seeing it.

I like how you went to the troubleshooting page, so, since I can't
seem to get both Firefox 35 and 39 going at the same time, here is
my *entire* screen after performing the following:

$ killall firefox
$ rm ~rf $HOME/.mozilla
$ ./firefox39/firefox/firefox &
OK the default browser nag screen and press alt-h to get to the menu
and open up the troubleshooting page:
(snap picture)

(repeat and rinse with firefox 35).

Here is the result, with Firefox 39 on the left, and 35 on the right.
run only seconds apart:

http://i.imgur.com/RMoJW86.jpg

Clearly, *nothing* has changed on my system, yet, the newer firefox
opens up with HUGE zoom and HUGE decorations, while the older firefox
is just perfect.

[Dave Pyles]

I think Karlheinz is the only one.

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 19:21:31 -0400, Dave Pyles wrote:

> I think Karlheinz is the only one.

Actually, I'm only slowly realizing that the two bugs are the *same*
bug, which cropped up in the switch between FF37 and FF38.
http://i.imgur.com/RMoJW86.jpg

Look at that composite full-screen screenshot, taken only moments
apart after deleting the ~/.mozilla directory and restarting the
second version of Firefox.

It seems that the two observations:
1. HUGEZOOM level, and,
2. HUGEBORDERS

Are, apparently, exactly the same bug.
The default Firefox 39 window itself is what is huge.
http://i.imgur.com/RMoJW86.jpg

Even the About Firefox version popup is huge, in comparison:
http://i.imgur.com/h63JydT.jpg

Measuring with my fingers, it's about 1-1/2 times *BIGGER*.

What do you make of this easily repeatable observation?

[Ed Mullen]

Not here, FF 40.0 Beta.

--
Ed Mullen
http://edmullen.net/
An American is a person who isn't afraid to criticize the President but
is always polite to traffic cops.

[WaltS48]

Clearly looks messed up.

I created a new user on my system. This creates a new Home folder for
that user.

Opened the Canonical installed 38.0 which created a new .mozilla folder
with a new default profile.

Downloaded and extracted 29.0 to the Downloads folder.

Renamed the Downloads/firefox folder to fx29.

Created a launcher on my desktop pointing to ~/Downloads/fx29/firefox -p
-new-instance. -p -new-instance opens the profile manager, where I
created a test29 profile which I used to open Fx29.

Same procedure for Fx 36.0.4, renaming the firefox folder fx36, launcher
pointing to ~/Downloads/fx36/firefox -p -new-instance, created a test36
profile when the profile manager opened which I used for Fx36.

That is how I had 3 different versions running at the same time.

[url=http://kb.mozillazine.org/Profile_Manager]Profile Manager -
MozillaZine Knowledge Base[/url]

[url=https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options]Command
Line Options - Mozilla | MDN[/url]

The Command line options page indicates the user should use; firefox
-new-instance -P "Another Profile"

[Caver1]

So there is no difference on YOUR computer.

--
Caver1

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 18:27:48 -0400, Ed Mullen wrote:

> Not here, FF 40.0 Beta.

What is your operating system?

[Caver1]

noremote

--
Caver1

[Caver1]

At this point we don't know because we don't have your system.
You were shown that the different versions all have the same space usage
on everyone else's system.
There is something one your system that is causing this.

--
Caver1

[Caver1]

There is no bug. It's something on your system that is causing this.
Why won't you accept that?
Go ahead and ignore everything everyone is telling you. We know nothing.

--
Caver1

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 20:22:33 -0400, WaltS48 wrote:

> The Command line options page indicates the user should use; firefox
> -new-instance -P "Another Profile"

THANK YOU VERY MUCH for that suggestion!
http://i.imgur.com/LMm76LZ.jpg

Now, for the first time, I was able to run *both* a firefox-38-and-above
against a firefox-37-and-below at the *same* time on the *same* machine
under the exact *same conditions*!

As I have been saying all along, the change occurs in Firefox 37 to 38
with the way Firefox opens up.

What I only belatedly realized is that it's not the HUGE ZOOM level,
per se, but that it's just about 1.5 times the SIZE as shown here:
http://i.imgur.com/LMm76LZ.jpg

I appreciate you figuring that out, as people here are skeptical
of the most obvious things, so proof is required (which is fine).

We're using a similar version of Kubuntu (I'm on 14.04) so what
you try matters alot.

$ killall firefox
$ rm -rf $HOME/.mozilla
$ konsole
$ ./firefox_38.0/firefox/firefox -new-instance -P "firefox 38"
$ konsole
$ ./firefox_35.0.1/firefox/firefox -new-instance -P "firefox 39"

What else can I prove to you so that people believe that the *only*
thing that is changing here is the version of Firefox being run?

[»Q«]

In
<news:mailman.1677.143623083...@lists.mozilla.org>,

Karlheinz Fenstermacher <karlh...@cordiallynetwork.com> wrote:

> http://i.imgur.com/LMm76LZ.jpg
>
> Now, for the first time, I was able to run *both* a
> firefox-38-and-above against a firefox-37-and-below at the *same*
> time on the *same* machine under the exact *same conditions*!

For each of the two Firefoxes, please enter "about:buildconfig" into
the address bar, then paste the configure arguments here. (I
think it's a long shot that this might provide a clue, but a long shot
is worth it when it's as easy as a cut-and-paste.)

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 20:25:38 -0400, Caver1 wrote:

> So there is no difference on YOUR computer.

For every test I run, I get consistent results as shown below.
http://i.imgur.com/h63JydT.jpg

Every invocation of Firefox 37 and below works fine.
Every invocation of Firefox 38 and above is unusably large.

Here you see both versions running simultaneously.
http://i.imgur.com/LMm76LZ.jpg

The *only* difference is in the version of Firefox.

So, if the problem is "my" operating system, what test would I
run to prove your assumption?

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 20:30:27 -0400, Caver1 wrote:

> At this point we don't know because we don't have your system.
> You were shown that the different versions all have the same space usage
> on everyone else's system.
> There is something one your system that is causing this.

While that may be true, it does NOT happen with *ANY* other program,
and not even with Firefox at or below version 37.

Here are the two versions run moments apart:
http://i.imgur.com/h63JydT.jpg

Here you see two versions running simultaneously.
http://i.imgur.com/LMm76LZ.jpg

The results are the same for all versions at or below 37,
and for all versions at or above 38.

The operating system did not change.
The only thing that changed was the version of Firefox.

What I don't get is that everyone is saying it's not a bug in Firefox.
What I don't understand is how can it _not_ be a bug in Firefox
(since everyone says it's not).

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 20:26:43 -0400, Caver1 wrote:

>> What's the trick to running two Firefox versions, side to side?
> noremote

Thanks for the advice.

I was able to run two versions side by side, which resulted in
exactly what I said was happening (so now I don't have to eat
my hat). :)

http://i.imgur.com/LMm76LZ.jpg

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 20:33:26 -0400, Caver1 wrote:

> There is no bug. It's something on your system that is causing this.
> Why won't you accept that?
> Go ahead and ignore everything everyone is telling you. We know nothing.

If I agree with you that it's *something* on my system, then I have
to *understand* your logic, since the only logic you've applied so
far is that the handful of people (none of whom are on the same OS
AFAICT) don't see the problem.

OK. That logic works (because you can assume that Mozilla would
know about this if it is a bug).

But, if it's on my system, and if NOTHING changes between invocation
of the two versions, then where how I look for the bug on "my" OS?

[WaltS48]

I will try your commands tomorrow, in my test user account. May add
Thunderbird so I don't have to switch back and forth between user
accounts to respond.

BTW "Another Profile" doesn't mean you put the profile name in quotes. A

Although the Profile Manager should still open allowing you to create a
new profile to test with.

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 20:30:04 -0500, »Q« wrote:

> For each of the two Firefoxes, please enter "about:buildconfig" into
> the address bar, then paste the configure arguments here. (I
> think it's a long shot that this might provide a clue, but a long shot
> is worth it when it's as easy as a cut-and-paste.)

Thank you for your advice on how to debug this Linux:Firefox issue.
Here is the requested information (warning, long lines)...

############################################################################
START FIREFOX version 39 LOG
############################################################################
Script started on Mon 06 Jul 2015 07:33:57 PM PDT
$ ./firefox_39.0/firefox/firefox -new-instance -P "Firefox 39" &
(process:28496): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
(process:28496): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:28496): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
[1]+ Done ./firefox_39.0/firefox/firefox -new-instance -P "Firefox 39"
exit
Script done on Mon 06 Jul 2015 07:37:29 PM PDT
----------------------------------------------------------------------------
Firefox 39 result of about:buildconfig
----------------------------------------------------------------------------
about:buildconfig
Build Machine

bld-linux64-spot-099
Source

Built from https://hg.mozilla.org/releases/mozilla-release/rev/d3b3e57e8088
Build platform
target
x86_64-unknown-linux-gnu
Build tools
Compiler Version Compiler flags
/builds/slave/rel-m-rel-l64_bld-000000000000/build/gcc/bin/gcc 4.7.3 -Wall -Wdeclaration-after-statement -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Werror=char-subscripts -Werror=comment -Werror=endif-labels -Werror=enum-compare -Werror=ignored-qualifiers -Werror=int-to-pointer-cast -Werror=multichar -Werror=nonnull -Werror=pointer-arith -Werror=pointer-sign -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=unknown-pragmas -Wno-unused -Wcast-align -Wno-error=uninitialized -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=coverage-mismatch -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe
/builds/slave/rel-m-rel-l64_bld-000000000000/build/gcc/bin/g++ 4.7.3 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Werror=endif-labels -Werror=int-to-pointer-cast -Werror=missing-braces -Werror=parentheses -Werror=pointer-arith -Werror=return-type -Werror=sequence-point -Werror=switch -Werror=trigraphs -Werror=type-limits -Werror=unused-label -Wno-invalid-offsetof -Wcast-align -Wno-error=uninitialized -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=coverage-mismatch -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -fprofile-use -fprofile-correction -Wcoverage-mismatch -O3 -fomit-frame-pointer
Configure arguments

--enable-update-channel=release --enable-update-packaging --with-google-api-keyfile=/builds/gapi.data --with-google-oauth-api-keyfile=/builds/google-oauth-api.key --with-mozilla-api-keyfile=/builds/mozilla-desktop-geoloc-api.key --enable-crashreporter --enable-release --enable-elf-hack --enable-stdcxx-compat --enable-warnings-as-errors --enable-official-branding

############################################################################
START FIREFOX version 38 LOG
############################################################################
Script started on Mon 06 Jul 2015 07:37:58 PM PDT

$ killall firefox
firefox: no process found
$ rm -rf $HOME/.mozilla
$ ./firefox_38.0/firefox/firefox -new-instance -P "Firefox 38" &
[1] 10738
(process:10738): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
(process:10738): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:10738): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
[1]+ Done ./firefox_38.0/firefox/firefox -new-instance -P "Firefox 38"
$ exit
exit

Script done on Mon 06 Jul 2015 07:40:45 PM PDT
----------------------------------------------------------------------------
Firefox 38 result of about:buildconfig
----------------------------------------------------------------------------
about:buildconfig
Build Machine

akateko
Build platform
target
x86_64-pc-linux-gnu
Build tools
Compiler Version Compiler flags
gcc 4.8.2 -Wall -Wdeclaration-after-statement -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe
c++ 4.8.2 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -freorder-blocks -Os -fomit-frame-pointer
Configure arguments

--host=x86_64-linux-gnu --prefix=/usr --libexecdir=/usr/lib/firefox --with-l10n-base=/build/buildd/firefox-38.0+build3/./l10n --srcdir=/build/buildd/firefox-38.0+build3/. --enable-release --disable-install-strip --disable-updater --enable-application=browser --enable-startup-notification --with-distribution-id=com.ubuntu --enable-optimize --enable-tests --enable-crashreporter --with-branding=browser/branding/official --disable-gnomevfs --enable-gio --enable-update-channel=release --disable-debug --disable-elf-hack --enable-gstreamer=1.0 --with-google-api-keyfile=/build/buildd/firefox-38.0+build3/debian/ga --with-google-oauth-api-keyfile=/build/buildd/firefox-38.0+build3/debian/go
############################################################################
START FIREFOX version 37 LOG
############################################################################
Script started on Mon 06 Jul 2015 07:40:52 PM PDT
$ killall firefox
firefox: no process found
$ rm -rf $HOME/.mozilla
$ ./firefox_37.0/firefox/firefox -new-instance -P "Firefox 37" &
[1] 16453
(process:16453): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
(process:16453): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:16453): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

[1]+ Done ./firefox_37.0/firefox/firefox -new-instance -P "Firefox 37"
$ exit
exit

Script done on Mon 06 Jul 2015 07:42:14 PM PDT
----------------------------------------------------------------------------
Firefox 37 result of about:buildconfig
----------------------------------------------------------------------------
about:buildconfig
Build Machine

bld-linux64-spot-117
Source

Built from https://hg.mozilla.org/releases/mozilla-release/rev/29182ac68a26
Build platform
target
x86_64-unknown-linux-gnu
Build tools
Compiler Version Compiler flags
/builds/slave/rel-m-rel-l64_bld-000000000000/build/gcc/bin/gcc 4.7.3 -Wall -Wdeclaration-after-statement -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Werror=char-subscripts -Werror=comment -Werror=endif-labels -Werror=enum-compare -Werror=ignored-qualifiers -Werror=int-to-pointer-cast -Werror=multichar -Werror=nonnull -Werror=pointer-arith -Werror=pointer-sign -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=unknown-pragmas -Wno-unused -Wcast-align -Wno-error=uninitialized -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=coverage-mismatch -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe
/builds/slave/rel-m-rel-l64_bld-000000000000/build/gcc/bin/g++ 4.7.3 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Werror=endif-labels -Werror=int-to-pointer-cast -Werror=missing-braces -Werror=parentheses -Werror=pointer-arith -Werror=return-type -Werror=sequence-point -Werror=switch -Werror=trigraphs -Werror=type-limits -Werror=unused-label -Wno-invalid-offsetof -Wcast-align -Wno-error=uninitialized -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=coverage-mismatch -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -fprofile-use -fprofile-correction -Wcoverage-mismatch -O3 -fomit-frame-pointer
Configure arguments

--enable-update-channel=release --enable-update-packaging --with-google-api-keyfile=/builds/gapi.data --with-google-oauth-api-keyfile=/builds/google-oauth-api.key --with-mozilla-api-keyfile=/builds/mozilla-desktop-geoloc-api.key --enable-crashreporter --enable-release --enable-elf-hack --enable-stdcxx-compat --enable-warnings-as-errors --enable-official-branding
############################################################################
START FIREFOX version 35 LOG
############################################################################
Script started on Mon 06 Jul 2015 07:42:18 PM PDT
$ killall firefox
firefox: no process found
$ rm -rf $HOME/.mozilla
$ ./firefox_35.0.1/firefox/firefox -new-instance -P "Firefox 35" &
[1] 19833
(process:19833): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
(process:19833): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
(process:19833): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised
(firefox:19833): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

[1]+ Done ./firefox_35.0.1/firefox/firefox -new-instance -P "Firefox 35"
$ exit
exit

Script done on Mon 06 Jul 2015 07:44:06 PM PDT
----------------------------------------------------------------------------
Firefox 35 result of about:buildconfig
----------------------------------------------------------------------------
about:buildconfig
Build Machine

bld-linux64-spot-099
Source

Built from https://hg.mozilla.org/releases/mozilla-release/rev/d3b3e57e8088
Build platform
target
x86_64-unknown-linux-gnu
Build tools
Compiler Version Compiler flags
/builds/slave/rel-m-rel-l64_bld-000000000000/build/gcc/bin/gcc 4.7.3 -Wall -Wdeclaration-after-statement -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Werror=char-subscripts -Werror=comment -Werror=endif-labels -Werror=enum-compare -Werror=ignored-qualifiers -Werror=int-to-pointer-cast -Werror=multichar -Werror=nonnull -Werror=pointer-arith -Werror=pointer-sign -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=unknown-pragmas -Wno-unused -Wcast-align -Wno-error=uninitialized -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=coverage-mismatch -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe
/builds/slave/rel-m-rel-l64_bld-000000000000/build/gcc/bin/g++ 4.7.3 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Werror=endif-labels -Werror=int-to-pointer-cast -Werror=missing-braces -Werror=parentheses -Werror=pointer-arith -Werror=return-type -Werror=sequence-point -Werror=switch -Werror=trigraphs -Werror=type-limits -Werror=unused-label -Wno-invalid-offsetof -Wcast-align -Wno-error=uninitialized -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=coverage-mismatch -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -fprofile-use -fprofile-correction -Wcoverage-mismatch -O3 -fomit-frame-pointer
Configure arguments

--enable-update-channel=release --enable-update-packaging --with-google-api-keyfile=/builds/gapi.data --with-google-oauth-api-keyfile=/builds/google-oauth-api.key --with-mozilla-api-keyfile=/builds/mozilla-desktop-geoloc-api.key --enable-crashreporter --enable-release --enable-elf-hack --enable-stdcxx-compat --enable-warnings-as-errors --enable-official-branding
############################################################################
"End of log file"
############################################################################

[Caver1]

On 07/06/2015 09:59 PM, Karlheinz Fenstermacher wrote:
> On Mon, 06 Jul 2015 20:33:26 -0400, Caver1 wrote:
>
>> There is no bug. It's something on your system that is causing this.
>> Why won't you accept that?
>> Go ahead and ignore everything everyone is telling you. We know nothing.
>
> If I agree with you that it's *something* on my system, then I have
> to *understand* your logic, since the only logic you've applied so
> far is that the handful of people (none of whom are on the same OS
> AFAICT) don't see the problem.
>
> OK. That logic works (because you can assume that Mozilla would
> know about this if it is a bug).

Mozilla devs don't always now about a bug until someone files a bug
report. Then if it can't be reproduced elsewhere there's not much that
can be done.

> But, if it's on my system, and if NOTHING changes between invocation
> of the two versions, then where how I look for the bug on "my" OS?
>

Who said it's the OS?
Haven't you ever seen a problem on one computer with the same OS as
another that doesn't have that same problem? Happens. Different
hardware, programs...
It could be a combination of factors. Not saying it is just pointing out
possibilities.
Could be the magnetic field around your house.

--
Caver1

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 22:50:06 -0400, WaltS48 wrote:

> I will try your commands tomorrow, in my test user account. May add
> Thunderbird so I don't have to switch back and forth between user
> accounts to respond.

Thanks Walt. I appreciate the help.

Obviously *something* is awry, and whatever it is, only shows up
between Firefox 37 and Firefox 38.

I had never created a user before, so, I created a new user as per
the instructions here:
https://www.digitalocean.com/community/tutorials/how-to-add-and-delete-users-on-an-ubuntu-14-04-vps

The results were exactly the same as they were with my regular account.
http://i.imgur.com/DYxTKth.jpg

> BTW "Another Profile" doesn't mean you put the profile name in quotes.

> Although the Profile Manager should still open allowing you to create a
> new profile to test with.

Ah. That's why it kept *asking* me for the profile name, even though
I had *thought* I had given it the profile name each time.

My mistake.

Thanks for explaining that, as yes, you are correct, it kept asking
me in the GUI what profile name to use and I gave it a unique name
each time.

Here is the log file from simultaneous testing of FF38 and FF37 on a
brand new user:

Note that I did not know about your quote hint, so I'm using the quotes
incorrectly below; but it shouldn't change the results.
############################################################################
Script started on Mon 06 Jul 2015 08:28:02 PM PDT

$ killall firefox
firefox: no process found

$ rm -rf $HOME/.mozilla

$ ./firefox_38.0/firefox/firefox -new-instance -P "Firefox 38" &

[1] 7506
(process:7506): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

(process:7506): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(firefox:7506): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

[1]+ Done ./firefox_38.0/firefox/firefox -new-instance -P "Firefox 38"

exit

Script done on Mon 06 Jul 2015 08:29:20 PM PDT
############################################################################
Script started on Mon 06 Jul 2015 08:29:50 PM PDT
firefox: no process found
[1] 7669
(process:7669): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

(process:7669): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(firefox:7669): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

[1]+ Done ./firefox_37.0/firefox/firefox -new-instance -P "Firefox 37"

exit

Script done on Mon 06 Jul 2015 08:30:39 PM PDT
############################################################################

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 23:00:38 -0400, Caver1 wrote:

> Could be the magnetic field around your house.

I agree it could be *something* on the computer.

All I can say, for sure, is that:
1. It happens with my user account.
2. It happens with a new user account.

Here, for example, is the result of FF38 & FF37 on a brand new virgin
user account: http://i.imgur.com/DYxTKth.jpg

The only thing that overtly changes is the FF version:
3. It happens with every FF version tested at or above version 38.
4. It does not happen with every FF version tested at or below 37.

[»Q«]

In
<news:mailman.1684.143623783...@lists.mozilla.org>,

Karlheinz Fenstermacher <karlh...@cordiallynetwork.com> wrote:

> On Mon, 06 Jul 2015 20:30:04 -0500, »Q« wrote:
>
> > For each of the two Firefoxes, please enter "about:buildconfig" into
> > the address bar, then paste the configure arguments here. (I
> > think it's a long shot that this might provide a clue, but a long
> > shot is worth it when it's as easy as a cut-and-paste.)
>
> Thank you for your advice on how to debug this Linux:Firefox issue.
> Here is the requested information (warning, long lines)...

Thanks, but I unfortunately I don't see any clues there.

[Karlheinz Fenstermacher]

On Mon, 06 Jul 2015 23:54:38 -0500, »Q« wrote:

> Thanks, but I unfortunately I don't see any clues there.

I do thank you very much for trying to help.
I apologize that I responded somewhat rudely and crudely to some people,
as I felt ridiculed, not believed, and made fun of.

I should NOT have let it get to me, but I had been reading and responding
to every concern, but, when the posts turned hateful, it was my mistake
to continue responding instead of plonking, which I have sensibly done
(which cut the post count that needed responses down by a lot!).

So, I do apologize for any harsh words I may have spoken in this thread.
I was so frustrated that everyone was telling me it couldn't be happening
when it was happening, coupled with the fact that I went on at least a
half dozen wild goose chases thinking it was the "customization" that I
had done.

In addition, I had thought there were two bugs, but, in reality, there is
only one problem.

1. Any version of Firefox tested at or above version 38 shows up about
twice the size it should be on my system, making it basically unusable on
a small laptop.

2. Any version of Firefox tested at or below version 37 works just fine.

So, the problem is solved, as I'll just use Firefox 37 moving forward.
Had I this clarity of the net result at the beginning of this
conversation, I never would have needed to even open the thread.

As such, I apologize for the inconvenience and I do appreciate all the
help. If there were a way to mark this SOLVED, we might want to consider
doing that since Firefox 37 does not exhibit the problem (which only
arose when I updated firefox from 37 to 38 in the first place).

Had I known how to downgrade Firefox in the beginning, again, this whole
thread would not have been needed. I apologize.

[WaltS48]

Starting Firefox from the command line I don't see these
GLib-GObject-WARNING messages.

Maybe you need to upgrade that package?

I do get:

(process:11304): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed

(process:11304): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed

But my Firefox 29.0, 36.0, just installed and tested 37.0, and 38.0 all
look the same.

I'm out.

[Karlheinz Fenstermacher]

On Tue, 07 Jul 2015 10:17:04 -0400, WaltS48 wrote:

> But my Firefox 29.0, 36.0, just installed and tested 37.0,
> and 38.0 all look the same.

Thanks Walt, for testing as I know it's work for you.
I guess I'm just lucky that my Firefox up to version 37 was well behaved
as my borders are smaller than everyone's.
It's only at Firefox 38 where things suddenly go bad.
But, the solution is simple so we can mark this solved now.
Firefox 37 works just fine.

Thank you very much for your kind help!

[WaltS48]

You are correct except for the 9 critical security vulnerabilities you
are exposed to using Firefox 37.0.

[Security Advisories for Firefox —
Mozilla](https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/)

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 08:17:27 -0500, Karlheinz Fenstermacher wrote:

Just to report an additional test, I installed FF39 on a WinXP
machine today, and the borders were just fine, as was the
window size.

So the firefox bug is just in the way FF38 and above handles
something in the Kubuntu trusty tahir operating system of mine.

Probably they never tested it properly.

[WaltS48]

Probably.

My Firefox 38.0 was updated to 39.0 today, and there was no change to
the Toolbar sizes and default page zoom level.

--
Kubuntu 14.10 | KDE 4.14.1 | Thunderbird 42.0a1(Daily) Go Bucs!
[Coexist · Understanding Across Divides](https://www.coexist.org/)
[Visit Pittsburgh](http://www.visitpittsburgh.com)

[Anthrocon 2015: Viking Invasion! | "Fur, Fun, And So Much
More!"](http://www.anthrocon.org/)July 9-12, 2015
[Pittsburgh Vintage Grand Prix -](http://www.pvgp.org/) July 10-19,2015

[Karlheinz Fenstermacher]

On Thu, 09 Jul 2015 10:08:05 -0400, WaltS48 wrote:

> My Firefox 38.0 was updated to 39.0 today, and there was no change to
> the Toolbar sizes and default page zoom level.

Thanks for checking Walt.
It seems that only on Kubuntu 14.04 (AFAWCT), *something* in the
operating system that Firefox 38 and above interacts with causes Firefox
38 and above to be about twice as large as it should be.

Something changed in Firefox, since I can reproduce the problem without
changing *anything* on my system, simply by loading Firefox 37 or below,
(which is what I'm stuck on, forever, until they fix this bug).

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 08:17:27 -0500, Karlheinz Fenstermacher wrote:

> In another thread, we proved the existence of an unknown-as-yet bug in
> Firefox 38 (Canonical distribution) & Firefox 39 (Mozilla distribution)
> which I am trying to determine what the cause is.
>
> A key unanswered question is:
>
> What controls the Firefox 38/39 border size & default page zoom level,
> and, did that change between Firefox 37 and 38?

Since I can't find anyone else in my local circle who has this problem, I
do realize it may be machine or operating system specific, so, I
definitely appreciate any and all debugging commands you can provide for
me to run and provide diagnostic results back to you.

I ran the following commands in sequence:
$ ./firefox_37.0/firefox/firefox -new-instance -P Firefox_37 -url http://
devicepixelratio.com/ &
$ ./firefox_38.0/firefox/firefox -new-instance -P Firefox_38 -url http://
devicepixelratio.com/ &
$ ./firefox_39.0/firefox/firefox -new-instance -P Firefox_39 -url http://
devicepixelratio.com/ &

The results were the following:
FF37: Your Device Pixel Ratio is: 1 (With no viewport set.)
FF38: Your Device Pixel Ratio is: 2 (With no viewport set.)
FF39: Your Device Pixel Ratio is: 2 (With no viewport set.)

Please see the attached screenshot of simultaneous FF37 & FF39 results on
Kubuntu 14.04:
firefox_37_vs_39_pixelratio_test_results.jpg
http://i.imgur.com/FbN0Uu4.jpg

[Karlheinz Fenstermacher]

On Tue, 21 Jul 2015 21:52:56 -0500, Karlheinz Fenstermacher wrote:

> I ran the following commands in sequence:
> $ ./firefox_37.0/firefox/firefox -new-instance -P Firefox_37 -url
> http://
> devicepixelratio.com/ &
> $ ./firefox_38.0/firefox/firefox -new-instance -P Firefox_38 -url
> http://
> devicepixelratio.com/ &
> $ ./firefox_39.0/firefox/firefox -new-instance -P Firefox_39 -url
> http://
> devicepixelratio.com/ &
>
> The results were the following:
> FF37: Your Device Pixel Ratio is: 1 (With no viewport set.)
> FF38: Your Device Pixel Ratio is: 2 (With no viewport set.)
> FF39: Your Device Pixel Ratio is: 2 (With no viewport set.)

Turns out, it's a bug in the pixdev code that firefox uses to figure out
the screen's pixel resolution...

https://bugzilla.mozilla.org/show_bug.cgi?id=1186145

The workaround is simply to turn off automatic pixdev calculation, and to
simply manually set the pixdev number to "1" (from a default of "-1.0"
which means to let Firefox calculate it), where "1" is 96 dpi (you can
change that, but 1 worked nicely for me).

So, (a) it's a known bug, and (b) there is a known workaround.

Thanks for all your help, advice, and suggestions!

[Karlheinz Fenstermacher]

On Sun, 05 Jul 2015 11:20:08 -0400, Caver1 wrote:

> If you discovered a bug did you report it?

https://bugzilla.mozilla.org/show_bug.cgi?id=1186145

[Karlheinz Fenstermacher]

Some people are questioning whether Firefox uses GTK (it does).
Here are the details.

Requirements to compile firefox from its sources, page:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Linux_Prerequisites

A recent POSIX Shell

A C++ compiler. GCC 4.7 or higher is required. Again, please note that
as of Firefox 38, GCC 4.6 and earlier are no longer supported, and will
not work; your platform's native compiler may work, provided it supports
those features of C++11 that the Firefox codebase relies on, which are
listed >here<. (Firefox 37 requires GCC 4.6 or higher).

Perl 5.6 or higher. Older perl versions may work if you upgrade
File::Spec to version 0.8

Python 2.7.3 or later. Python 3 will not work.
GNU make 3.80 or higher. Other varieties of "make" will not work.
The GTK2 widget toolkit, version 2.10 or higher
^^^^
As of Firefox 42, the GTK3 widget toolkit, version 3.4 or higher
^^^^
(rest of the requirements skipped)

So currently it is built against GTK2 but starting with future
release 42, they will switch to GTK3
https://bugzilla.mozilla.org/show_bug.cgi?id=975919

[Karlheinz Fenstermacher]

In the Firefox bug report, the developer requested I run a GTK3
app as a test, as shown below:

https://bugzilla.mozilla.org/show_bug.cgi?id=1186145
FROM THE DEVELOPER:
"Can you try installing some other GTK3 app and see if it's using a
scale ratio of 2.0? E.g. a newish version of nautilus or the like?"

My nautilus is version 3:
$ nautilus --version
=> GNOME nautilus 3.10.1

Do those of you who know Linux better than I do have a suggested
app that I can run which uses GTK3? I don't know which apps use
GTK3 (as I never heard of GTK until this bug came up)?

[thez...@gmail.com]

Hi Karlheinz,
I have the very same bug on Debian Sid 64 with KDE 5. I use Iceweasel and Icedove, the Debian specific counterparts of Firefox and Thunderbird, and starting from version 38, both have the same problem you reported.

> In the Firefox bug report, the developer requested I run a GTK3
> app as a test, as shown below:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1186145
> FROM THE DEVELOPER:
> "Can you try installing some other GTK3 app and see if it's using a
> scale ratio of 2.0? E.g. a newish version of nautilus or the like?"

I started i.e. roxterm with gtk3 interface and it looks correct.

> Do those of you who know Linux better than I do have a suggested
> app that I can run which uses GTK3? I don't know which apps use
> GTK3 (as I never heard of GTK until this bug came up)?

you can find some apps searching for gtk3 with apt:
apt-cache search gtk3

then you can install one of them and try to execute it.

For what I can see it seems to me a problem related to HiDPI... it seems that Firefox and Thunderbird dont't feel the correct screen resolution and size, so appears as you had a smaller screen