Announcement

Collapse
No announcement yet.

Firefox-62.0 slow to compile ?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Firefox-62.0 slow to compile ?

    I saw that the source for firefox-62.0 was out, so I downloaded. Previous version I've built was 62.0beta20. I use a patch for system harfbuzz and system graphite2, so the first thing I did was diff the sources to see if anything relevant to that or the other system versions had changed - no. Started the build, left it. From time to time checked, still building. Eventually used 'top', at that point 'ld' was running so it was only using 100% cpu and finished shortly after.

    This is a Ryzen 1300X, with beta20 and -j4 the build and install had taken under 47 minutes. With 62.0 release, almost 131 minutes for ./mach build. Installed that, works fine, but thought I'd done something wrong in the build, or maybe --verbose was slowing it. Fresh source, dropped caches, retried without the patch : still building, not using more than 100% CPU (i.e. only one core) in either rustc or cc1plus, MOZ_MAKE_FLAGS=-j4 definitely exported.

    LFS/BLFS-8.3, gcc-8.2.0, llvm/clang 6.0.1, rustc-1.25.0. Kernel, if it matters, is 4.18.3 (and all are unchanged since I built beta20).

  • #2
    Firefox team maybe help you..

    Comment


    • #3
      Maybe, but like most bugs it will probably just sit around unless it happens to a lot of people. It did get moved from Untriaged and Firefox to General and Firefox Build System.

      I suspect I might have seen similar odd behaviour in the past, but I might have been thinking of when I was compiling rust. Both use python for the build system, both seem to often be erratic. My experience when building both of them in scripts is that they can fail because of errors, but somehow return a status of success (i.e. true) to a script which invoked them.

      Comment


      • #4
        Surely, Its very obvious that, the new version of firefox is very slow to compile it with other softwares. This is probably happens because when you start downloading a new version there may be a bug that creates certain error to file and thus it needs more and more time to get compiled. So, Just service your device and attach it with good antivirus protection.

        Comment


        • #5
          Originally posted by Bates357 View Post
          Surely, Its very obvious that, the new version of firefox is very slow to compile it with other softwares. This is probably happens because when you start downloading a new version there may be a bug that creates certain error to file and thus it needs more and more time to get compiled. So, Just service your device and attach it with good antivirus protection.
          What? Say that again. I don't understand what you mean.

          Comment


          • #6
            Originally posted by Bates357 View Post
            Surely, Its very obvious that, the new version of firefox is very slow to compile it with other mobdro softwares. This is probably happens because when you start downloading a new version there may be a bug that creates certain error to file and thus it needs more and more time to get compiled. So, Just service your device and attach it with good antivirus protection.
            I mean, I also feel that Firefox-62.0 is slow to compile.

            Comment


            • #7
              Originally posted by Bates357 View Post

              I mean, I also feel that Firefox-62.0 is slow to compile.
              OK sure. But explain why you think it might be caused by corrupt download? I'm confused by that and why you think a antivirus could help?

              Comment


              • #8
                Meanwhile, I've now seen similar issues with 62.0.2 and 63.0b8 - but only on the Ryzen 1300X. The build of 62.0.2 was mostly very slow (fell back to only 100% CPU), but eventually speeded up to using 400% near the end. With 63 I've been using rustc-1.29.0, first build (clang) was very slow but eventually failed (possibly something in my choice of system libs). Went back to gcc-8.2.0, it was back to 400% a lot of the time.

                I still think the (python) build system is unpredictable, but at least with both rustc and firefox-63 compile failures seem to propagate out and stop my build, which is much better than how things were a few months ago.

                Comment


                • #9
                  Originally posted by zerothruster View Post
                  I saw that the source for firefox-62.0 was out, so I downloaded. Previous version I've built was 62.0beta20. I use a patch for system harfbuzz and system graphite2, so the first thing I did was diff the sources to see if anything relevant to that or the other system versions had changed - no. Started the build, left it. From time to time checked, still building. Eventually used 'top', at that point 'ld' was running so it was only using 100% cpu and finished shortly after.

                  This is a Ryzen 1300X, with beta20 and -j4 the build and install had taken under 47 minutes. With 62.0 release, almost 131 minutes for ./mach build. Installed that, works fine, but thought I'd done something wrong in the build, or maybe --verbose was slowing it. Fresh source, dropped caches, retried without the patch : still building, not using more than 100% CPU (i.e. only one core) in either rustc or cc1plus, MOZ_MAKE_FLAGS=-j4 definitely exported.

                  LFS/BLFS-8.3, gcc-8.2.0, llvm/clang 6.0.1, rustc-1.25.0. Kernel, if it matters, is 4.18.3 (and all are unchanged since I built beta20).

                  Firefox team maybe help you.. best water purifier

                  Comment


                  • #10
                    Another Firefox downloaded to my MacBook Air (61.0.1). Not exclusively are enter components missing in this new plan (where is the line of most visited locales that utilization to be close to the highest point of the window?), however, this thing is moderate and nonresponsive. It can take up to a moment to stack the landing page - something that used to happen quickly. Furthermore, there are directions that simply don't work by any means - or possibly they appear not to work by any stretch of the imagination.

                    What did you do? For what reason is this rendition so profoundly not the same as all the awesome past ones? I need to utilize and bolster Firefox, however, I can't utilize this one by any means. I have downloaded blackmart apk and then I got how to do and a big relief I got.

                    Comment

                    Working...
                    X