CodeSite Viewer 5.3.4 : apparent system hang on windows 10, in user32.DrawTextW

Home Forums CodeSite CodeSite Viewer 5.3.4 : apparent system hang on windows 10, in user32.DrawTextW

Viewing 1 reply thread
  • Author
    Posts
    • #2206
      WARREN POSTMA
      Participant

        I am seeing CodeSite Viewer hanging with high CPU usage on Windows 10, it’s 100% repeatable ON MY SYSTEM but probably won’t be repeatable on other peoples systems and is probably (but not certainly) a bug in Windows 10 itself, and a low level issue with GDI+ and a specific video driver.

        Steps:

         

        1. start codesite file viewer 5.3.4, by double clicking a CSL file (5 megs or so, not too big).

        2. Open and start browsing.  Codesite operates normally for a few seconds.

        3. After several hundred scroll or search operations have worked normally, the system hangs, often after Ctrl-F searching moves the position within the file.

        4.  Attach BDS.exe to process to see where it is.

         

        The function (whatever it is at 61c586a7) in TextShaping.dll appears to be consuming 100% CPU and never exits.    Breakpoint at :005910f2 +n are never hit.

        :61c586a7 ; C:\Windows\System32\TextShaping.dll
        :61c5d5e6 ; C:\Windows\System32\TextShaping.dll
        :61c56c54 ; C:\Windows\System32\TextShaping.dll
        :61c55fc0 ; C:\Windows\System32\TextShaping.dll
        :61c51e91 ; C:\Windows\System32\TextShaping.dll
        :61c3e303 ; C:\Windows\System32\TextShaping.dll
        :61c3acbc ; C:\Windows\System32\TextShaping.dll
        :61c2c3fb ; C:\Windows\System32\TextShaping.dll
        :7688be6a ; C:\Windows\System32\gdi32full.dll
        :7688aaf0 ; C:\Windows\System32\gdi32full.dll
        :7688a409 ; C:\Windows\System32\gdi32full.dll
        :7688a2c8 ; C:\Windows\System32\gdi32full.dll
        :7688a04e ; C:\Windows\System32\gdi32full.dll
        :76887408 ; C:\Windows\System32\gdi32full.dll
        :768867ff ; C:\Windows\System32\gdi32full.dll
        :76886050 gdi32full.LpkDrawTextEx + 0x30
        :75fa9f0d ; C:\Windows\System32\user32.dll
        :75fa9da4 ; C:\Windows\System32\user32.dll
        :75fa98db ; C:\Windows\System32\user32.dll
        :75fa969f user32.DrawTextW + 0x3f
        :005910f2 ; C:\Program Files (x86)\Raize\CS5\Bin\CSFileViewer_5_3_4.exe
        :005999c1 ; C:\Program Files (x86)\Raize\CS5\Bin\CSFileViewer_5_3_4.exe
        :50ae558f vcl250.@Vcl@Controls@TControl@WMMouseMove$qqrr24Winapi@Messages@TWMMouse + 0x83
        :50ae9848 ; C:\Program Files (x86)\Raize\CS5\Bin\vcl250.bpl
        :50ae8e13 vcl250.@Vcl@Controls@TWinControl@MainWndProc$qqrr24Winapi@Messages@TMessage + 0x2f
        :5016ebce rtl250.@System@Classes@TDataModule@WriteHeight$qqrp22System@Classes@TWriter + 0x22
        :75fbd9cb user32.AddClipboardFormatListener + 0x4b

         

        I suspect a Win32/GDI+/video driver bug.
        Machine: Windows 10, Intel UHD graphics, dxdiag full output available on request.

        Card name: Intel(R) UHD Graphics 630

        Driver File Version: 26.20.0100.7985 (English)

        Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b0ce3b6fbdab301d\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b0ce3b6fbdab301d\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b0ce3b6fbdab301d\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b0ce3b6fbdab301d\igd12umd64.dll

        Driver Version: 26.20.100.7985
        DDI Version: 12
        Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.6

        Recent Windows 10 updates (wmic qfe list):

        Caption CSName Description FixComments HotFixID InstallDate InstalledBy InstalledOn Name ServicePackInEffect Status
        http://support.microsoft.com/?kbid=4570721 WARRENDELLXPS Update KB4570721 NT AUTHORITY\SYSTEM 9/3/2020
        http://support.microsoft.com/?kbid=4537759 WARRENDELLXPS Security Update KB4537759 5/11/2020
        http://support.microsoft.com/?kbid=4557968 WARRENDELLXPS Security Update KB4557968 5/11/2020
        http://support.microsoft.com/?kbid=4559309 WARRENDELLXPS Update KB4559309 NT AUTHORITY\SYSTEM 8/29/2020
        http://support.microsoft.com/?kbid=4561600 WARRENDELLXPS Security Update KB4561600 NT AUTHORITY\SYSTEM 7/17/2020
        http://support.microsoft.com/?kbid=4566785 WARRENDELLXPS Security Update KB4566785 NT AUTHORITY\SYSTEM 7/17/2020
        http://support.microsoft.com/?kbid=4570334 WARRENDELLXPS Security Update KB4570334 NT AUTHORITY\SYSTEM 8/12/2020
        http://support.microsoft.com/?kbid=4566782 WARRENDELLXPS Update KB4566782 NT AUTHORITY\SYSTEM 8/12/2020

        I will post back if I figure anything more out about this.  Frankly, any Delphi app having ANY output to a win32 window can hang through no fault of its own code.

        If I find a workaround it will probably be an upgrade/downgrade of a video driver.  Every delphi app ever written calls user32.DrawTextW. I can’t imagine this being an actual bug in Raize’s codebase.

      • #2251
        Ray Konopka
        Keymaster

          Hi Warren,

          I apologize for the late response. Apparently, the forum software marked your post as needing approval, and of course, did not send a notification that approval was needed. I just happened to be browsing the settings when I discovered your pending messages.
          Thank you for posting the detailed information. Unfortunately, I have not heard of any other reports like this, and I have not experienced it myself. However, I have made a note of it to keep an eye on this situation.

          Again, I apologize for the mix-up with the post.

          Ray

      Viewing 1 reply thread
      • You must be logged in to reply to this topic.