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

Randomly happening ?"kernel corruption"? exposed on both testbots by "Wine Test, Module: user32, Test: scroll"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Win32SS
    • Labels:

      Description

      Both testbots VBox and KVM had a hangup in "Wine Test, Module: user32, Test: scroll" when testing 0.4.14-RC-2-g824f887
      https://build.reactos.org/#/builders/9/builds/26974

      Running Wine Test, Module: user32, Test: scroll
      (win32ss/user/ntuser/scrollbar.c:98) err: IntGetSBData Wrong Extra bytes for CTL Scrollbar!
      
      Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault)
      Memory at 0x00000008 could not be read: Page not present.
      kdb:>
       bt
      Eip:
      <win32k.sys:6d3e8 (win32ss/user/ntuser/scrollbar.c:223 (IntCalculateThumb))>
      Frames:
      <win32k.sys:6dae3 (win32ss/user/ntuser/scrollbar.c:708 (co_IntGetScrollBarInfo))>
      <win32k.sys:6e212 (win32ss/user/ntuser/scrollbar.c:1226 (NtUserGetScrollBarInfo))>
      <ntoskrnl.exe:13ccee (ntoskrnl/include/internal/i386/ke.h:730 (KiSystemServiceHandler))>
      <ntoskrnl.exe:3d29 (:0 (KiFastCallEntry))>
      <ntdll.dll:fe6d>
      <user32.dll:1d79c>
      <user32.dll:1da79>
      <user32_winetest.exe:c3027>
      <user32_winetest.exe:11b8ec>
      <user32_winetest.exe:11cb0a>
      <user32_winetest.exe:11cb53>
      <kernel32.dll:116e2>
      kdb:>
      

      When I did nothing but reschedule building+testing that exact same revision, the problem did not happen again:
      https://build.reactos.org/#/builders/9/builds/26976

      I don't want to create an unactionable/unretestable ticket, but I fear that this may point to severe kernel corruption that is randomly happening. I was unsure, whether filing a ticket for such a flaky thing makes sense, but hBelusca agreed to create one. I suspect the underlaying issue can also affect master.

      The first two commits that went into the 0.4.14RC did behave fine when they were applied to 0.4.13RCs, so I do not think they are related:
      0.4.14-RC-2-g824f887
      0.4.14-RC-1-g0fbebb8

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bug zilla Bug Zilla
                Reporter:
                reactosfanboy reactosfanboy
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: