Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-15793

RosBE2.1.6 configure step takes very long

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 0.4.15
    • SDK
    • None

    Description

      0.4.11-RC-36-gc5204e3 gcc dbg linux

      VBox4.3.12 (no GA) + 1000MB RAM + 10GB FAT32 partition

      Reproduction steps
      -use a fresh ros installation
      download and install git from rapps, use the git-cmd
      'git config --system http.sslverify false'
      'git clone https://github.com/reactos/reactos.git' (took 44min) master head 2019-02-25 23:00 (got commit 0.4.12-dev-753-g6ee2f98)
      download & install ROSBE 2.1.6 from rapps
      start the taskmgr and let it run
      configure starts and runs until "Configure done" gets displayed, it did not return to prompt
      after maybe 30mins-1h, before configure usually returns to the prompt, it started to log repeatedly

      (ntoskrnl/mm/ARM3/pfnlist.c:632) Legacy Mm eating ARM3 page!.

      After now more than 48h it still did not return to the prompt.
      -The system is not totally frozen yet:
      -the green caret in the RosBE prompt is still blinking and I can move the mouse, I can even drag the RosBE window.
      -The time in systray is updating normally.
      -the green VBox LED is indicating read activity now and then
      -But taskmanager does not update its Window content anymore at all, since >40h. I can not drag or activate the taskmgr window anymore.

      0.4.11-RC-36-gc5204e3.log
      0.4.11-RC-36-gc5204e3.png
      After 24hours of waiting I intentionally broke into debugger to collect some stacktraces and conted afterwards.

      Attachments

        1. 0.4.10-dev-230-g12713b7__AlsoOSFreezeAfterSomeHours.log
          1.71 MB
          reactosfanboy
        2. 0.4.10-dev-230-g12713b7__AlsoOSFreezeAfterSomeHours.png
          50 kB
          reactosfanboy
        3. 0.4.11-RC-36-gc5204e3.log
          1.77 MB
          reactosfanboy
        4. 0.4.11-RC-36-gc5204e3.png
          63 kB
          reactosfanboy
        5. 0.4.12-dev-1060-gb714290__stacksamples.log
          1.74 MB
          reactosfanboy
        6. 0.4.12-RC-55-g3a6cb85_1930.png
          53 kB
          reactosfanboy
        7. 0.4.12-RC-55-g3a6cb85_2050.png
          53 kB
          reactosfanboy
        8. 0.4.12-RC-55-g3a6cb85_2140_dead.png
          52 kB
          reactosfanboy
        9. 0.4.12-RC-55-g3a6cb85_systemfreeze.log
          1.70 MB
          reactosfanboy
        10. 0.4.15-dev-382-g3cb8ee6_Configure_55min.log
          2.08 MB
          reactosfanboy
        11. 0.4.15-dev-382-g3cb8ee6_Configure_55min.png
          50 kB
          reactosfanboy
        12. 0.4.15-dev-5199-g227e596_configureFinished_After_6min_OK.png
          70 kB
          reactosfanboy
        13. 0.4.15-dev-5199-g227e596_gitClone28min_gitReset4min_OK.png
          65 kB
          reactosfanboy
        14. 0.4.15-dev-5199-g227e596_OK.log
          3.28 MB
          reactosfanboy
        15. 0.4.15-dev-5199-g227e596_ourMemoryManagerUnderExtremePressure_DuringConfigure_OK.png
          72 kB
          reactosfanboy
        16. ros_on_ros_112.png
          147 kB
          DougLyons
        17. ros_on_ros_203.png
          130 kB
          DougLyons

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. CORE-18516 Regression, building ros on ros RosBE2.1.6 'ninja bootcd -j1' does fail since some 0.4.15-dev commit at step237 during compiling boot/environ with random errors

          • Major - Major loss of function.
          • Open
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. CORE-18014 pseudo-memory leak of ~ 4kb per second, observable in taskmgrs performance tab, triggered by the heap.c changes

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. CORE-18196 Process Hacker from RAPPS doesn't start anymore

          • Major - Major loss of function.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CORE-15080 MM is still inferior, no swapping, MS .NET4 install reproducibly crashes the OS with just 128MB RAM, but WinXP is teachers pet

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. CORE-14588 Optimize RtlpFindAndCommitPages

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. CORE-14917 Implement delayed close support in FastFAT

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              zefklop jgardou
              reactosfanboy reactosfanboy
              Votes:
              6 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: