Overclock.net › Forums › Software, Programming and Coding › Other Software › Waterfox 56.0.1: 13 December [Free, open and private web browser.]
New Posts  All Forums:Forum Nav:

Waterfox 56.0.1: 13 December [Free, open and private web browser.] - Page 490

post #4891 of 7373
Quote:
Originally Posted by nevets1219 View Post

For those wondering, I've tried a new profile and that seems to have improved situations and I had thought the problem solved. But after playing some Borderlands the issue came back again. I think it's related to KB2670838 and hardware acceleration in Firefox / Waterfox. At the moment, I've uninstalled KB2670838 - hopefully that's the problem. Do you guys have hardware acceleration disabled in Waterfox (see Options > Advanced > General)?
I really wanted this to be the magic bullet which solved my micro-stuttering issue but unfortunately, disabling hardware acceleration and restarting the browser anew did not relieve it of its momentary freezes.

Thank you for the suggestion, however. The more we know the better off everyone is.
post #4892 of 7373
I'm guessing you don't have that update installed as well? I've uninstalled that but kept hardware acceleration enabled as it was fine before. I'd suggest a new profile to see if that helps, sometimes updates do the weirdest things.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 930 ASUS P6X58D Premium EVGA GTX 670 FTW Sig2 Corsair 3x2GB 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 2TB Samsung BD Windows 7 Ultimate 64bit Samsung PX2370 
PowerCase
Corsair AX750 CoolerMaster HAF 932 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 930 ASUS P6X58D Premium EVGA GTX 670 FTW Sig2 Corsair 3x2GB 
Hard DriveOptical DriveOSMonitor
WD Caviar Black 2TB Samsung BD Windows 7 Ultimate 64bit Samsung PX2370 
PowerCase
Corsair AX750 CoolerMaster HAF 932 
  hide details  
Reply
post #4893 of 7373
For those of us awaiting v19, within the last hour there has been a new entry in the Waterfox project feed

http://www.waterfoxproject.org/news/fullnews.php?fn_id=57

and it says
Quote:
People must be wondering most of the time when the next version of Waterfox is coming. Unfortunately that's not an answer I can give directly. With each version comes new bugs (mostly compiler bugs) that takes time to fix. At the moment another compiler bug has been found and I'm working closely with Mozilla/Intel as I always do to sort it out.

So in review, Waterfox gets released when all the bugs are sorted out, which is usually 1-2 weeks depending on the severity. I work every day to sort these problems out, so hopefully everyone understands the delays.

Thanks,

Alex
post #4894 of 7373
I appreciate why MrAlex doesn't bother to post updates in this thread any more, considering every single time I read it seems there's some or other new troll post here.

Something I was wondering however, based on the below:
Quote:
Originally Posted by SpodoCommodo View Post

People must be wondering most of the time when the next version of Waterfox is coming. Unfortunately that's not an answer I can give directly. With each version comes new bugs (mostly compiler bugs) that takes time to fix. At the moment another compiler bug has been found and I'm working closely with Mozilla/Intel as I always do to sort it out.

So in review, Waterfox gets released when all the bugs are sorted out, which is usually 1-2 weeks depending on the severity. I work every day to sort these problems out, so hopefully everyone understands the delays.

Thanks,

Alex

If the current version of the Intel compiler has show-stopping bugs every time he tries to release a new version... why not simply go back to using the old one which didn't have all these issues?
Core i7 Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 930 @ 2.93 GHz Gigabyte X58A-UD3R (Rev. 1.0) PALIT GTX 760 Jetstream 12GB DDR3 1600 Mhz (6x2GB) 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 Samsung HD103UJ Samsung HD103SJ Samsung HD204UI 
Optical DriveOSMonitorPower
LiteOn iHAS524 DVD RW Windows 7 Ultimate 64bit SP1 ViewSonic VX2260WM Seasonic X-Series 650W SS-650KM3 
Case
Cooler Master 690 II Advanced RC-692A-KKN5 
  hide details  
Reply
Core i7 Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 930 @ 2.93 GHz Gigabyte X58A-UD3R (Rev. 1.0) PALIT GTX 760 Jetstream 12GB DDR3 1600 Mhz (6x2GB) 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 Samsung HD103UJ Samsung HD103SJ Samsung HD204UI 
Optical DriveOSMonitorPower
LiteOn iHAS524 DVD RW Windows 7 Ultimate 64bit SP1 ViewSonic VX2260WM Seasonic X-Series 650W SS-650KM3 
Case
Cooler Master 690 II Advanced RC-692A-KKN5 
  hide details  
Reply
post #4895 of 7373
Because the new compiler has new functionality and features, and if he doesn't find the bugs now, they'll be there later when the current compiler is defunct, and will probably be there in the next ver (probably 2015 given their current release patterns).

We probably won't see 19, but barring any new issues introduced in 20, or 19.0.1/2, we'll get one of those.
post #4896 of 7373
Quote:
Originally Posted by EliasAlucard View Post

Waterfox 15 still doesn't have a unique user agent string, but uses the Firefox user agent:

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:15.0) Gecko/20120830 Firefox/15.0

^^ Please fix this, so that it can be identified how many people are actually using Waterfox. This is what the UA in PaleMoon looks like:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110619 Firefox/3.6.18 (Palemoon/3.6.18)

I see no good reason why Waterfox shouldn't have its own user agent string.
Hi... remember the user agent string I talked about a while ago? Have you added a unique user agent string yet, to Waterfox? I'm asking because of this plugin I'm coding for vBulletin forums:

UADisplay: http://www.vbulletin.org/forum/showthread.php?t=295667

To make things simpler, I suggest the following user agent string for Waterfox:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Waterfox/19.0

Don't do it like Pale Moon, because that will confuse Google Analytics etc., and just count your browser as Firefox. With the user agent string I've suggested, not only will it make your browser more known/popular, it will also give it some recognition on forums.

Thanks.
post #4897 of 7373
Quote:
Originally Posted by JayBart View Post

The 1st week of Feb. on here you said you were not going to use WF anymore because of the crashing,and would wait till ver.19,what happened to that?

What happened to that is that I still keep waiting for v19 to give it another try, since the superior/newst compiler should in theory give the best results (that's why I was so surprised to see that it currently isn't on top in all benchmarks I ran).

Quote:
Originally Posted by EliasAlucard View Post

Don't do it like Pale Moon, because that will confuse Google Analytics etc., and just count your browser as Firefox. With the user agent string I've suggested, not only will it make your browser more known/popular, it will also give it some recognition on forums.

I don't know if MrAlex just forgot to change the ua or if it was a deliberate decision - but if it's the latter I like it because a more unique ua string makes users easier to track, and many people still don't know about this (or don't use the ua switcher plugin).

Personally I don't think ua strings are for advertising a browser flavor, but to let website devs see what engines are used and test their site accordingly - and all custom compiles waterfox/cyberfox/palemoon use the mozilla engine with the version that already is in the ua.
Edited by Marsu24 - 3/9/13 at 6:44am
post #4898 of 7373
Quote:
Originally Posted by EliasAlucard View Post

Hi... remember the user agent string I talked about a while ago? Have you added a unique user agent string yet, to Waterfox? I'm asking because of this plugin I'm coding for vBulletin forums:

UADisplay: http://www.vbulletin.org/forum/showthread.php?t=295667

To make things simpler, I suggest the following user agent string for Waterfox:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Waterfox/19.0

Don't do it like Pale Moon, because that will confuse Google Analytics etc., and just count your browser as Firefox. With the user agent string I've suggested, not only will it make your browser more known/popular, it will also give it some recognition on forums.

Thanks.

There was discussion on this a while back, it happened then was reverted because the UA change broke many websites.
Core i7 Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 930 @ 2.93 GHz Gigabyte X58A-UD3R (Rev. 1.0) PALIT GTX 760 Jetstream 12GB DDR3 1600 Mhz (6x2GB) 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 Samsung HD103UJ Samsung HD103SJ Samsung HD204UI 
Optical DriveOSMonitorPower
LiteOn iHAS524 DVD RW Windows 7 Ultimate 64bit SP1 ViewSonic VX2260WM Seasonic X-Series 650W SS-650KM3 
Case
Cooler Master 690 II Advanced RC-692A-KKN5 
  hide details  
Reply
Core i7 Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 930 @ 2.93 GHz Gigabyte X58A-UD3R (Rev. 1.0) PALIT GTX 760 Jetstream 12GB DDR3 1600 Mhz (6x2GB) 
Hard DriveHard DriveHard DriveHard Drive
Samsung 830 Samsung HD103UJ Samsung HD103SJ Samsung HD204UI 
Optical DriveOSMonitorPower
LiteOn iHAS524 DVD RW Windows 7 Ultimate 64bit SP1 ViewSonic VX2260WM Seasonic X-Series 650W SS-650KM3 
Case
Cooler Master 690 II Advanced RC-692A-KKN5 
  hide details  
Reply
post #4899 of 7373
Really, WOW64 for a 64bit browser? drunken.gif

If NOT having WOW64 in the UA is an issue with a website, then it stands to reason that the 100's of millions of people still using 32bit windows would have a problem with that website
post #4900 of 7373
Quote:
Originally Posted by RealityRipple View Post

Because the new compiler has new functionality and features, and if he doesn't find the bugs now, they'll be there later when the current compiler is defunct, and will probably be there in the next ver (probably 2015 given their current release patterns).

We probably won't see 19, but barring any new issues introduced in 20, or 19.0.1/2, we'll get one of those.

Totally wrong approach. A developer should never go on a new tool/library/api as soon as this comes out. What you do is to try and ensure that your current projects continue to run and be updated. If this is viable with the old Intel compiler, you continue with the old intel compiler. AT THE SAME TIME, you have a new project using the new compiler. For anyone having used a CVS system, you have the HEAD with old compiler and a BRANCH with the new compiler. You continue your project from the HEAD and at the same time, the BRANCH is used to ensure that your current project will get to the point that it is working fine with the new compiler. When the code is mature enough to be compiled with the new intel compiler, you MERGE the branch to the HEAD and you are ready to go. These are fundamentals in software development and release engineering. And with Waterfox, everything is done in the wrong way.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Other Software
Overclock.net › Forums › Software, Programming and Coding › Other Software › Waterfox 56.0.1: 13 December [Free, open and private web browser.]