Discussion about official Mozilla Firefox builds
arewesnappyyet.com will eventually become a link farm. .org would avoid this...
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
Would there be a weekly report blog post like one we currently have with Memshrink? Since e10s is out of the way, I think MemShrink, Snappy, should be on Top Priority.
Yes, as mentioned under the "Momentum" heading on https://etherpad.mozilla.org/snappy
Who told you that? This thread is about responsiveness not memory usage.
Also, the regressions identified about the increase in usage has already been filed and assigned.
Latest: Firefox/49.0.1 *ESR/45.4.0 - Mobile/49.0.1 - Thunderbird/45.3.0 - SeaMonkey/2.40
Nightly: Nightly/52.0a1 - Mobile/52.0a1 - Daily/50.0a1 - SeaMonkey/2.43a1
http://magneticpudding.com/ <- My Blog
i5 3570k @ 4.5 Ghz / NV 660 / 32GB DDR3 / 1080p LCD / SSD (120 + 180) / W8 ||| Atom N270 / NV ION / 3GB DDR3 / SSD / 1366x768 / W8
you're absolutely right mate
Firefox Release | Win8.1 x64 | AMD 6300 4Ghz x6 | AMD R9 270 2 GB for 1080p IPS | 4 GB RAM
Not impossible. If you disable the stupid tab closing animations then responsiveness goes way up.
Hey now! Lets not get carried away! They already took my rearranging animations away, and now you suggest removing my closing animations?
Sigh, a fella can dream can't he?
Is there some kind of architectural issue with animations in Firefox? Just asking naively.
Hopefully the Snappy team will also be interested in these Flash Multimedia issues https://bugzilla.mozilla.org/show_bug.cgi?id=702485 like i describe here my recent test shows also Addons can amplify these issues majorly depending on the Playback Scenario involved im pretty sure such Performance issues will be hardly trackable with talos
Im currently working on several local test cases (especially GPU (DSP) driven) to show how the percepted Performance impact can be especially with D2D @ low power rendering (Current Generation IGP entry level Intel HD2000 GT1) with different interactive content in a windowed environment.
Sure Adobe pretty much accepted the dead of Flash but Websites with content wont move that majorly fast over to HTML5 Multimedia it will take time and in that transition time Flash Player Scenarios will be of importance and percepted Performance a big issue, and there still will be a lot of content delivered in Flash still and not move to HTML5 in anyway
Also these issues are more General then Framework specific they will also be a problem for HTML5 content delivery and the perception of Browser Quality.
Adobe hasn't declared Flash dead, Adobe declared Flash too difficult to deploy for mobile.
Who is online
Users browsing this forum: No registered users and 4 guests