dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1584

chachazz
Premium Member
join:2003-12-14

1 edit

7 recommendations

chachazz

Premium Member

[Firefox] Firefox 36.0.1

Coming to a release server soon.

(Candidate Builds 1 and 2 are up)

Edit:
Here's the Release Notes: »www.mozilla.org/en-US/fi ··· senotes/

• Fixed- 36.0.1 - Disable the usage of the ANY DNS query type (1093983)
• Fixed - 36.0.1 - Fixed a startup crash with EMET (1137050)
• Fixed - 36.0.1 - Hello may become inactive until restart (1137469)
• Fixed - 36.0.1 - Print preferences may not be preserved (1136855)
• Fixed - 36.0.1 - Hello contact tabs may not be visible (1137141)
• Fixed - 36.0.1 - Accept hostnames that include an underscore character ("_") (1136616)
• Fixed - 36.0.1 - WebGL may use significant memory with Canvas2d (1137251)
• Fixed - 36.0.1 - Option -remote has been restored (1080319)
• Fixed - 36.0.1 - Fix a top crash


All downloads - »www.mozilla.org/en-US/fi ··· fox/all/

StuartMW
Premium Member
join:2000-08-06

StuartMW

Premium Member

Thanks for the heads-up.

Nothing on the FTP site--yet.

Davesnothere
Change is NOT Necessarily Progress
Premium Member
join:2009-06-15
Canada

3 edits

Davesnothere to chachazz

Premium Member

to chachazz
 
Thanks.

So what did Moz get wrong THIS time ? (in 36.0)

= = = = =

BTW, folks watch for the PORTABLE edition soon, here :

»sourceforge.net/projects ··· e%20Ed./

EDIT : Portable is now UP !

mark5019
Premium Member
join:2002-03-30
Atlanta, GA

mark5019 to chachazz

Premium Member

to chachazz
not up yet

Phoenix22
Death From Above
Premium Member
join:2001-12-11
SOG C&C Nrth

1 edit

2 recommendations

Phoenix22 to Davesnothere

Premium Member

to Davesnothere
pretty much all of it..........+++++pinholed your firewall/router, etc.
WWa
join:2011-09-02

WWa to Davesnothere

Member

to Davesnothere
Looking through the list of bugs fixed in 36.0.1, I see "Hello" bugs, WinXP SP2 bugs, -remote option restored, a "massive memory leak", bugs in the new DNS-related code, print settings not saved, and several top crashes.
»hg.mozilla.org/releases/ ··· shortlog

therube
join:2004-11-11
Randallstown, MD

therube

Member

Which bug was the "massive memory leak"?

And there is also the "underscore" issue, »bugzilla.mozilla.org/sho ··· =1136616.

You know, they are so concerned about change - for the sake of change, they have totally lost robust & stable. They really need to fire everyone & start again.

StuartMW
Premium Member
join:2000-08-06

StuartMW to chachazz

Premium Member

to chachazz
Full 36.0.1 installer on the FTP site. No internal update as of yet.
WWa
join:2011-09-02

WWa to therube

Member

to therube
1137251 - Massive memory leak with Firefox 36+ (maybe related to WebGL)

Buddel
If it ain't broke, don't fix it.
Premium Member
join:2004-03-06
EU

1 recommendation

Buddel to chachazz

Premium Member

to chachazz
Just got it via the internal updater.

Racerbob
Premium Member
join:2001-06-24
Webster, NY
·Frontier FiberOp..

3 recommendations

Racerbob to chachazz

Premium Member

to chachazz
Mozilla releases beta after beta after beta when they are working on a new version and features that many hard core users do not want. Then they release a final build and it still isn't right. This accelerated release schedule needs to be slowed down. Way down. Just my opinion.

StuartMW
Premium Member
join:2000-08-06

1 recommendation

StuartMW to Buddel

Premium Member

to Buddel
Click for full size
said by Buddel:

Just got it via the internal updater.

As did I

jadinolf
I love you Fred
Premium Member
join:2005-07-09
Ojai, CA

1 recommendation

jadinolf

Premium Member

Same here.
Sentinel
Premium Member
join:2001-02-07
Florida

1 recommendation

Sentinel to chachazz

Premium Member

to chachazz
Thank you

Davesnothere
Change is NOT Necessarily Progress
Premium Member
join:2009-06-15
Canada

Davesnothere to Racerbob

Premium Member

to Racerbob
said by Racerbob:

Mozilla releases beta after beta after beta when they are working on a new version and features that many hard core users do not want. Then they release a final build and it still isn't right. This accelerated release schedule needs to be slowed down. Way down. Just my opinion.

 
Bob, get in line behind ME with that PoV !
Bobby_Peru
Premium Member
join:2003-06-16

Bobby_Peru

Premium Member

said by Davesnothere:

said by Racerbob:

Mozilla releases beta after beta after beta when they are working on a new version and features that many hard core users do not want. Then they release a final build and it still isn't right. This accelerated release schedule needs to be slowed down. Way down. Just my opinion.

 
Bob, get in line behind ME with that PoV !

Luddites...

Davesnothere
Change is NOT Necessarily Progress
Premium Member
join:2009-06-15
Canada

1 recommendation

Davesnothere

Premium Member

said by Bobby_Peru:

Luddites...

 
I resemble that remark ! - And proud OF it !
PX Eliezer1
Premium Member
join:2013-03-10
Zubrowka USA

2 recommendations

PX Eliezer1 to Racerbob

Premium Member

to Racerbob
said by Racerbob:

Mozilla releases beta after beta after beta when they are working on a new version and features that many hard core users do not want. Then they release a final build and it still isn't right. This accelerated release schedule needs to be slowed down. Way down. Just my opinion.

That's why I got off the Mozilla Foundation merry-go-round, and use PaleMoon.

Rogue Wolf
An Easy Draw of a Sad Few
join:2003-08-12
Troy, NY

Rogue Wolf to chachazz

Member

to chachazz
It'd be nice if they fixed the problem that's sprung up with using YouTube's HTML5 player. It's gagging on long videos now. I thought I was free of Flash....

Davesnothere
Change is NOT Necessarily Progress
Premium Member
join:2009-06-15
Canada

Davesnothere to PX Eliezer1

Premium Member

to PX Eliezer1
said by PX Eliezer1:

That's why I got off the Mozilla Foundation merry-go-round, and use PaleMoon.

 
You mean the Mozilla-go-Round !
Frodo
join:2006-05-05

Frodo to Rogue Wolf

Member

to Rogue Wolf
said by Rogue Wolf:

It'd be nice if they fixed the problem that's sprung up with using YouTube's HTML5 player.

This is their first attempt, at a release version. I was able to get VP9 out of Youtube.


I had to set media.mediasource.enabled to true. If the content comes in VP9, it should be using about 60% of the bandwidth that a H264 video would be using, a 40% savings. There is the html player, and then there is the html player with VP9 enabled. If you're good to go, then the Youtube html5 webpage will show all blue checkmarks.

Otherwise, you're using a bandwidth wasting browser.

MarkRH
Premium Member
join:2005-02-08
Edmond, OK

MarkRH

Premium Member

Might also check media.mediasource.webm.enabled as it was set to false by default for me.
Sentinel
Premium Member
join:2001-02-07
Florida

Sentinel to Frodo

Premium Member

to Frodo
This is interesting. I never heard anything about these settings. What do they do? Should they be enabled? If so then why are they not by default?
Frodo
join:2006-05-05

Frodo

Member

I toggled all four of mine to true. I think the media.mediasource.webm.enabled turns on the VP9. I believe FX36 has a partial implementation of this webm/vp9 usable on Youtube only. As far as I'm concerned, they can't roll out bandwidth saving technologies fast enough. I think it will result in more content.

While there may be some things, such as this port 1900 that has gone awry for me, this VP9 is an example of how the browser is going in the right direction too.

therube
join:2004-11-11
Randallstown, MD

1 recommendation

therube

Member

VP9 is a codec.
Webm is a container.

Virtually everything Youtube "webm" is now VP9 (as opposed to VP8 or earlier) & has been for some time now.
Frodo
join:2006-05-05

Frodo to chachazz

Member

to chachazz
The beta notes mention Youtube.
quote:
Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube
I don't see it in the final notes

But, it would be working if, when watching a video, rightclick the video and view stats for nerds. It will show the codec. I'm not seeing VP9 on Palemoon, for example.

Phoenix22
Death From Above
Premium Member
join:2001-12-11
SOG C&C Nrth

1 edit

Phoenix22 to Racerbob

Premium Member

to Racerbob
thatz not the only thing we could do.............
as much as i like my bud from gladiator.............
folks, we need to vet the damn release b4 everbody spends daze in a daze.......tryin' 2figure out wtf........i/you did wrong now........
when in fact it was the vendor...........now, frankly, i'm gun shy........w/o seein' whatz what b4 i jump...........itz nice 2know who packed your reserve chute too!

On top of all that .......itz a full moon release...............oh sure i will.........not!

Rogue Wolf
An Easy Draw of a Sad Few
join:2003-08-12
Troy, NY

1 edit

Rogue Wolf to Frodo

Member

to Frodo
Bandwidth isn't the problem. In any video over about 9 minutes or so, the HTML5 player will eventually stutter, freeze, try to load, and then end the video. Even if I allow the video to load fully beforehand, it does this. Some people have apparently gotten around this problem by disabling hardware accelerating, but it happens to me either way.

EDIT: I applied the changes recommended by Sentinel See Profile and they seem to have fixed the problem, as well as another one (only having 360p and 720p available).
Sentinel
Premium Member
join:2001-02-07
Florida

Sentinel

Premium Member

Those all sound like good reasons to enable the 2 settings that are off by default, but that does not explain why they are off by default to begin with. If they are so good and and enable functionality that is desirable then why are they not enabled by default? There must be some kind of potential downside. What is that downside?
Frodo
join:2006-05-05

1 edit

1 recommendation

Frodo

Member

said by Sentinel:

There must be some kind of potential downside. What is that downside?

I think the downside is, it might not be finished product. The Chromium browsers are running with it, no problem. I use Iron, no problem. At some point, I think Firefox will have finished product as well. They had notes about this in the beta but not in the final. So, that tells me it is still a work in progress.

Edit: Checking the FX 37 release notes, I see:
quote:
Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube.
That was the same thing showing in the 36 beta notes. So, that means they didn't get all the bugs out in time for FX36 final, best I can tell.