Recommended Posts

hmm why would firefox start doing this without updating and any changes to settings/drivers/hardware.

SfZgX.jpg

tried fresh profiles, reinstalling firefox and video drivers. issue is on both 32 and 64 builds and does not occur on other browsers.

incase anyone has this issue, I solved it by removing windows update kb 2670838 that came with IE10.

Azure and DLBI both sped up rendering, you can see as much from tests.

No disrespect Decryptor, and not because your a Mod, but because you seem a really cool guy here in the forums, those are just benchmarkings that in real life matter little. again 1ms faster, oh my god!!!

It's like when they implemented "Load tabs only when selected", that was just to hide the poor performance on Firefox when booting!!!

The feature is nice but it's timing was exactly when people were complaining about start times. And yet on a i5 2500k, with 16GB Ram, and Nvidia 570, with this option off and no tabs to load, Firefox can take 5 seconds to load. Now you might say, "Oh but 5 seconds pass on a blink of an eye", yes but IE9/10 is instant, why can't Firefox be too.

And this is just one example, if sure if I think a little harder, I'll find many more!

Now don't think I'm hatting Firefox, cause I'm not, I want it to be faster on all levels, but Mozilla seems more focused their own OS and mobile stuff than what made them popular on the first place, their DESKTOP BROWSER!!!

I'm not talking about 1ms here or there, I'm talking about things getting 10x faster (One "benchmark" went from 1fps to about 30fps on my Mac with the SVG DLBI stuff) In the best case, it won't help much (because it's already the best case), in the worse case you see a huge improvement.

And on my computer (Which funnily enough is an i5 200k with 16GB of RAM and a GTX 570) Firefox launches in <2 seconds (Nightly is closer to 1s, but it also has less tabs/extensions to load)

Edit: And their mobile stuff is driving desktop enhancements, All the work on off the main thread compositing (for example) is driven by a need to make the mobile UI more responsive, work of which also applies to the desktop.

In Inbound:

JS Engine (related to self-hosted code): https://bugzilla.mozilla.org/show_bug.cgi?id=784293

Bug introduced after Per Window Private Browsing: https://bugzilla.mozilla.org/show_bug.cgi?id=822056 , https://bugzilla.mozilla.org/show_bug.cgi?id=822008 , https://bugzilla.mozilla.org/show_bug.cgi?id=819510

Ion Monkey: https://bugzilla.mozilla.org/show_bug.cgi?id=822042

Image Decoding performance improvement (Snappy): https://bugzilla.mozilla.org/show_bug.cgi?id=811891

Session File read on Background thread (Snappy) - But Backout: https://bugzilla.mozilla.org/show_bug.cgi?id=532150

Compartment JS Inline: https://bugzilla.mozilla.org/show_bug.cgi?id=773911 (Improved CSS performance on Talos)

Imagelib related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=801061 , https://bugzilla.mozilla.org/show_bug.cgi?id=821448

Shutdown Improvement: https://bugzilla.mozilla.org/show_bug.cgi?id=818739 (Snappy P1 bug - vastly improved shutdown on Talos)

JS Engine - Ion Monkey - Array related Performance Improvement: https://bugzilla.mozilla.org/show_bug.cgi?id=821816

Baseline Compiler Preparation: https://bugzilla.mozilla.org/show_bug.cgi?id=821707

Download Panel View Downloads in Library (Landed but Backout): https://bugzilla.mozilla.org/show_bug.cgi?id=675902

JS Engine - ES6 improvement (landed but Backout): https://bugzilla.mozilla.org/show_bug.cgi?id=820180

Ion Monkey - Baseline Compiler related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820084

Web Audio API related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820875

JS Engine - Maps: https://bugzilla.mozilla.org/show_bug.cgi?id=817368

Related to Windows 8: https://bugzilla.mozilla.org/show_bug.cgi?id=821679 , https://bugzilla.mozilla.org/show_bug.cgi?id=821454

New YARR related performance win in v8-RegExp: https://bugzilla.mozilla.org/show_bug.cgi?id=808245

(Paris Bindings) WebIDL bug: https://bugzilla.mozilla.org/show_bug.cgi?id=821438 , https://bugzilla.mozilla.org/show_bug.cgi?id=819904 , https://bugzilla.mozilla.org/show_bug.cgi?id=818379 , https://bugzilla.mozilla.org/show_bug.cgi?id=816375 , https://bugzilla.mozilla.org/show_bug.cgi?id=816380 , https://bugzilla.mozilla.org/show_bug.cgi?id=820902

Per Window Private Browsing: https://bugzilla.mozilla.org/show_bug.cgi?id=818732

JS Engine: https://bugzilla.mozilla.org/show_bug.cgi?id=821151 , https://bugzilla.mozilla.org/show_bug.cgi?id=808148

Generational GC - Exact Rooting: https://bugzilla.mozilla.org/show_bug.cgi?id=816779

Ion Monkey: https://bugzilla.mozilla.org/show_bug.cgi?id=814966

Should I post regarding Important bugs landed but backout like currently did or not?

  • Like 2

the more info, the better!

Then I will cover backout information of Important bugs like I do as well since it sometime indicate that they will land sooner in exception cases it is not but majorly it is. So it will be help for users I think.

Thanks Zlip :)

I'm not talking about 1ms here or there, I'm talking about things getting 10x faster (One "benchmark" went from 1fps to about 30fps on my Mac with the SVG DLBI stuff) In the best case, it won't help much (because it's already the best case), in the worse case you see a huge improvement.

But that's the problem, You're assuming in the worst case you'll see huge improvements, when in fact the "laggy UI" is still there, what good is a 1000hp engine is, if the body can't hold more than 100hp without starting to fall apart?

In most i5 and i7 the problem is just hidden because of so much HP, but as soon as you get a less performance CPU and a intregrated GPU you'll notice how laggy Firefox UI is! The body is just top heavy!

And on my computer (Which funnily enough is an i5 200k with 16GB of RAM and a GTX 570) Firefox launches in <2 seconds (Nightly is closer to 1s, but it also has less tabs/extensions to load)

I'm not seeing that in my end, sure if you "open a new window" with Firefox as a process sure, but closing Firefox and re-opening it does take seconds and not 1.

Edit: And their mobile stuff is driving desktop enhancements, All the work on off the main thread compositing (for example) is driven by a need to make the mobile UI more responsive, work of which also applies to the desktop.

I think that decision is wrong and that's why we are where we are.

It should be the Desktop browser the priority.

Seriously how many users does Mozilla mobile have? On the iPhone? There's no Firefox browser (I have to use Opera)... On the Windows Phone? Not that I know about.. On Android? How many? 100k? 200k? A million?

How many Firefox Desktop users? Chrome is eating Firefox share and they are concerned with a very small % of their users on mobile platforms (and like I said before not even that many, actually just one, Android) and then they backport changes to Desktop months latter, if ever?

And using the few resources (man power) they have to build their own mobile OS? Great another dead project from the start! There's already 3 main OS's for mobile, then there's RIM, ex-Palm, etc... There's just no point!

This is Mozilla wanting to be relevant in other areas. But not only are they failing on doing so, they are neglecting their champion!

[update] Firefox Mobile share in %: http://marketshare.h...d=0&qpcustomd=1 0.1%

  • Like 2

Just curious, is this a known bug, or just some glitch on my end?

The generic addon icons are missing:

~snip~

its missing from my plugins page of addon manager as well. I will dig into bugzilla to find bug related to this.

From Inbound:

OS X Flash Crash: https://bugzilla.mozilla.org/show_bug.cgi?id=804606

MemShrink (basically DMD tuning and new memory reporter): https://bugzilla.mozilla.org/show_bug.cgi?id=819817 , https://bugzilla.mozilla.org/show_bug.cgi?id=821577 , https://bugzilla.mozilla.org/show_bug.cgi?id=818060

Canvas 2D Spec bug: https://bugzilla.mozilla.org/show_bug.cgi?id=803124

unprefixing of Gradients in FF Theme: https://bugzilla.mozilla.org/show_bug.cgi?id=821968 , https://bugzilla.mozilla.org/show_bug.cgi?id=821971

(Kind of Refactoring of code going on - Backout also) ImageLib bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=815471 , https://bugzilla.mozilla.org/show_bug.cgi?id=816362 , https://bugzilla.mozilla.org/show_bug.cgi?id=816374 , https://bugzilla.mozilla.org/show_bug.cgi?id=821023

Crash fix in DOM: https://bugzilla.mozilla.org/show_bug.cgi?id=820373

Cleanup in Encoding Menu (Show only standard encoding): https://bugzilla.mozilla.org/show_bug.cgi?id=805374

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

Crash in Layout: https://bugzilla.mozilla.org/show_bug.cgi?id=696640

Top Crash in Layers: https://bugzilla.mozilla.org/show_bug.cgi?id=813024

SVG Invalidation in DLBI: https://bugzilla.mozilla.org/show_bug.cgi?id=802628

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

SVG Performance regression when HWA is ON: https://bugzilla.mozilla.org/show_bug.cgi?id=820061

CSS Background mess up when HWA is OFF: https://bugzilla.mozilla.org/show_bug.cgi?id=819915

New Downloads View in Library (Relanded): https://bugzilla.mozilla.org/show_bug.cgi?id=675902

Related to XPCOM cleanup: https://bugzilla.mozilla.org/show_bug.cgi?id=820182

Paris Bindings (WebIDL): https://bugzilla.mozilla.org/show_bug.cgi?id=821593

  • Like 3

Posting only two bug currently because these are SUPER AMAZING::

https://bugzilla.moz...g.cgi?id=815748

https://bugzilla.moz...g.cgi?id=799315

It is to enable system wide codec to support MP3 and H.264 codecs for Windows Vista+, it is preferred off due to few reasons.

To enable it, go to about:config and toggle this to true:

media.windows-media-foundation.enabled

Remember it is in Inbound which is not merged to mozilla-central yet so try it after one or two days.

  • Like 2

What I like the most about using Nightly builds is that you never know what fixes are included untill hours after you update.

I think we can track the builds from TBPL and see which Nightly build cooking and then estimate with update release time. Means build take times. So overall not very surprise process for me at least.

I think we can track the builds from TBPL and see which Nightly build cooking and then estimate with update release time. Means build take times. So overall not very surprise process for me at least.

This is true but there was a time when the builds thread was updated as it should be. I long for those days. Without the updates all they need to do is post the change log for the build.

This is true but there was a time when the builds thread was updated as it should be. I long for those days. Without the updates all they need to do is post the change log for the build.

Agree!!!!

what you should do is just copy what Arjen or Peter6 Nightly Threads ( Bugs etc ) an Paste it into the forum, that way i wouldnt have to visit Mozillazine forum anymore

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
    • I have not even heard of that game. will take a look
    • Chasys Photo 5.41.01 by Razvan Serea Chasys Photo is a suite of image editing applications including a layer-based image editor with adjustment layers, linked layers, timeline and frame-based animation, icon editing, image stacking and comprehensive plug-in support (Chasys Photo Editor), a fast image viewer (Chasys Photo Viewer) and a fast multi-threaded image file converter (Chasys Photo Converter) , with RAW image support in all components. It supports the native file formats of several competitors including Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr, and the whole suite is designed to make effective use of multi-core processors, touch-screens and pen-input devices. Designed under the mantra of “unique, flexible and powerful”, Chasys Photo takes a radically different approach to image editing with the aim of opening up new possibilities for those who dare to be different. Chasys Photo key features: Free-style layering with blending modes Adjustment layers with multiple adjustments per layer Linked layers (a.k.a Linked Smart Objects) Composite, Image List, Frame Animation and Object Animation image modes Animation, both frame-based and object-based (timeline animation) Animation Composer engine Image Stacking for noise reduction, super-resolution, etc. Tablet/Pen-input/Stylus support with pressure control Touch-screen support with gestures including pitch-to-zoom and multi-finger panning Support for the native formats of Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr Support for common formats such as JPEG, animated PNG, animated GIF, TIFF, PICT, WebP, HEIF, DDS, JPEG-2000, JPEG-XR, JPEG-XL, AVI video, etc. Support for the OpenRaster interchange file format and rare formats such as QOI, MNG/JNG and DPX Support for older formats such as PPM/PGM/PBM, PCX/DCX, PCD, TGA, COKE, etc. Comprehensive Camera RAW file support with live adjustment Extensive plug-in support with streamlined SDKs Support for Photoshop Filter Plug-ins (.8BF) Advanced printing and scanning engines PDF document generation Icon and cursor editing, import and export, including Vista-style and Mac-OS icons Screen Capture, including Video Screen Capture with multiple triggering modes Video capture from devices (e.g. TV/Video) Supports multi-core processors, High-DPI displays and Multiple Display setups Integrated File Browser, Bluetooth OBEX and in-built utilities (Calculator, Notepad) Shell integration with thumbnails and conflict detection Unlimited Undo/Redo and Asynchronous Auto-Save, with Just-in-time memory compression to save space Fully re-editable text with advanced styling and effects (TextArt) Full alpha channel through out the workflow with Alpha protection (a.k.a. transparency protection) Multiple language support with user-editable language files and translation assistant (Chasys Photo Language Studio) Anti-aliasing and super-sampling support in tools and paths* Smart-resizing (similar to seam-carving) Best-in-class post-edit heuristics anti-aliasing engine Physical measurement specification with display size detection via EDID Uses the latest CD5 specification with animation and multi-resolution Super-fast internal graphics engine (JpDRAW2) Full UNICODE support in all components Metadata save, restore and scale to imitate vector art Configurable Guides and Grids with Snap-to-Grid Smart-dither to custom palette Asynchronous preview rendering engine Pantone equivalent palettes for PMS 100 to 814-2x Automatic color naming ... and many more! Chasys Photo 5.41.01 changelog: New Features Layered images with multiple pages (Composite/Multi-page) Additional templates to support template-centric workflow New Layer Blend Mode: Inverse Luma Mask Horizon detection in Rotate Transform Cropping option when importing video Orientation options in QR Code Generator plug-in Solved angle ambiguities (CCW versus CW) Internal Improvements Improved graphics engine (JpDRAW2™ v26.05) Improved CD5 codec (v4.10, improved ACSC compression) Improved interpolation when downsizing images Improved motion detection in Video Capture Slightly lower memory usage (RAM is getting expensive!) File Support and Bug Fixes Improved PXZ file support (placeholders, blanks) [bug-fix] Memory leak in flt_JPEG.dll Download: Chasys Photo 5.41.01 | 46.1 MB (Freeware) View: Chasys Photo Home Page | Wikipedia Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!