The Issue with Delphi Runtime Packages and Windows 10 Creators Update

June 12, 2017

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Windows 10 Creators Update changes to DLL loading affects Delphi applications that use runtime packages. Here is in update on the problems and possible solutions.

Since Windows 10 Creators Update was released two months ago, we have started seeing reports of issues with runtime package (for example, https://quality.embarcadero.com/browse/ RSP-17972, where myself, Embarcadero support and R&D have chimed in), mostly while debugging applications. The issue is affecting applications that use runtime packages (BPL), not applications compiled as a single executable. In general terms, the problem affects all applications that use runtime packages, built with any version of Delphi (recent, old, or even the early ones). In most cases, the slowdown for end user application is relatively limited, however applications with runtime packages on network shares are affected. But what is happening?

The Core Issue: Optimized DLL Loading

Let's start with some background information. On the Windows operating system, dynamic linking (DLLs) support both load-time binding and full runtime binding (LoadLibrary). In both cases, when the DLL is generated it is has a table of entry points (export table). Any other library or executable referring to it has an import table referring to functions of that export table. Since the early days, when the Delphi compiler (and linker) generate a DLL or package library (BPL) by assembling multiple units in a single binary file, and do so by making functions and methods available by creating multiple sections in the export/import table. This was likely a minor linker optimization, and never had a real side effect.

Fast forward to Windows 10 Creators Update. Microsoft decided to rewrite the DLL loading code to make it parallel (different threads can load different libraries in parallel) to optimize applications loading. However this change has ended up affecting the loading of libraries with multiple sections in the export tables. Empirically, it looks like a BPL is loaded once for each segment. Now consider that most of the core Delphi BPL (rtl, vcl, fmx) have dozens and dozens of sections, and the result is libraries are loaded (and unloaded) dozens and dozens of times.

Here is a screenshot of the effect in the Event log (this is a single form FMX application):

While in this simple application on my machine it takes a couple of extra seconds, with larger applications having many runtime packages the effect on the debugger can be fairly extreme. Here is the full debugger log, with operations on packages (and other notable ones) marked in bold:

Thread Start: Thread ID: 12052. Process Project13.exe (13088)
Process Start: C:\Users\marco\Documents\Embarcadero\Studio\Projects\Win32\Debug\Project13.exe. Base Address: $00400000. Process Project13.exe (13088)
Module Load: Project13.exe. Has Debug Info. Base Address: $00400000. Process Project13.exe (13088)
Module Load: ntdll.dll. No Debug Info. Base Address: $76F40000. Process Project13.exe (13088)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $74520000. Process Project13.exe (13088)
Module Unload: KERNEL32.dll. Process Project13.exe (13088)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $74520000. Process Project13.exe (13088)
Module Load: KERNELBASE.dll. No Debug Info. Base Address: $73B80000. Process Project13.exe (13088)
Thread Start: Thread ID: 14596. Process Project13.exe (13088)
Thread Start: Thread ID: 2688. Process Project13.exe (13088)
Thread Start: Thread ID: 2076. Process Project13.exe (13088)
Module Load: rtl250.bpl. Has Debug Info. Base Address: $50050000. Process Project13.exe (13088)
Module Load: rtl250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: rtl250.bpl. Has Debug Info. Base Address: $01740000. Process Project13.exe (13088)
Module Load: rtl250.bpl. Has Debug Info. Base Address: $02170000. Process Project13.exe (13088)
Module Unload: rtl250.bpl. Process Project13.exe (13088)
Module Unload: rtl250.bpl. Process Project13.exe (13088)
Module Unload: rtl250.bpl. Process Project13.exe (13088)
Module Load: OLEAUT32.dll. No Debug Info. Base Address: $74980000. Process Project13.exe (13088)
Module Load: msvcp_win.dll. No Debug Info. Base Address: $76130000. Process Project13.exe (13088)
Module Load: ucrtbase.dll. No Debug Info. Base Address: $743A0000. Process Project13.exe (13088)
Module Load: combase.dll. No Debug Info. Base Address: $75EA0000. Process Project13.exe (13088)
Module Load: RPCRT4.dll. No Debug Info. Base Address: $73A30000. Process Project13.exe (13088)
Module Load: SspiCli.dll. No Debug Info. Base Address: $73A10000. Process Project13.exe (13088)
Module Load: CRYPTBASE.dll. No Debug Info. Base Address: $73A00000. Process Project13.exe (13088)
Module Load: bcryptPrimitives.dll. No Debug Info. Base Address: $76810000. Process Project13.exe (13088)
Module Load: SECHOST.dll. No Debug Info. Base Address: $763A0000. Process Project13.exe (13088)
Module Load: ADVAPI32.dll. No Debug Info. Base Address: $73AF0000. Process Project13.exe (13088)
Module Load: msvcrt.dll. No Debug Info. Base Address: $75DE0000. Process Project13.exe (13088)
Module Load: USER32.dll. No Debug Info. Base Address: $76870000. Process Project13.exe (13088)
Module Load: win32u.dll. No Debug Info. Base Address: $74A20000. Process Project13.exe (13088)
Module Load: GDI32.dll. No Debug Info. Base Address: $74A50000. Process Project13.exe (13088)
Module Load: gdi32full.dll. No Debug Info. Base Address: $74640000. Process Project13.exe (13088)
Module Load: imagehlp.dll. No Debug Info. Base Address: $74060000. Process Project13.exe (13088)
Module Load: SHLWAPI.dll. No Debug Info. Base Address: $745F0000. Process Project13.exe (13088)
Module Load: ole32.dll. No Debug Info. Base Address: $74080000. Process Project13.exe (13088)
Module Load: WS2_32.dll. No Debug Info. Base Address: $73E20000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $031A0000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $031A0000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $031A0000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $031A0000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
      Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $01940000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02570000. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Unload: fmx250.bpl. Process Project13.exe (13088)
Module Load: VERSION.dll. No Debug Info. Base Address: $73990000. Process Project13.exe (13088)
Module Load: NETAPI32.dll. No Debug Info. Base Address: $712F0000. Process Project13.exe (13088)
Module Load: MPR.dll. No Debug Info. Base Address: $72BB0000. Process Project13.exe (13088)
Module Load: SHFOLDER.dll. No Debug Info. Base Address: $737E0000. Process Project13.exe (13088)
Module Load: SHELL32.dll. No Debug Info. Base Address: $74A80000. Process Project13.exe (13088)
Module Load: WINHTTP.dll. No Debug Info. Base Address: $72B00000. Process Project13.exe (13088)
Module Load: WSOCK32.dll. No Debug Info. Base Address: $72A00000. Process Project13.exe (13088)
Module Load: OLEACC.dll. No Debug Info. Base Address: $6F3D0000. Process Project13.exe (13088)
Module Load: CFGMGR32.dll. No Debug Info. Base Address: $73D50000. Process Project13.exe (13088)
Module Load: OPENGL32.dll. No Debug Info. Base Address: $6F2F0000. Process Project13.exe (13088)
Module Load: SHCORE.dll. No Debug Info. Base Address: $73D90000. Process Project13.exe (13088)
Module Load: GLU32.dll. No Debug Info. Base Address: $70C90000. Process Project13.exe (13088)
Module Load: netutils.dll. No Debug Info. Base Address: $71C70000. Process Project13.exe (13088)
Module Load: Windows.Storage.dll. No Debug Info. Base Address: $769B0000. Process Project13.exe (13088)
Module Load: AppCore.dll. No Debug Info. Base Address: $73B70000. Process Project13.exe (13088)
Module Load: POWRPROF.dll. No Debug Info. Base Address: $760E0000. Process Project13.exe (13088)
Module Load: profapi.dll. No Debug Info. Base Address: $74970000. Process Project13.exe (13088)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $00D10000. Process Project13.exe (13088)
Module Load: COMDLG32.dll. No Debug Info. Base Address: $742A0000. Process Project13.exe (13088)
Module Load: COMCTL32.dll. No Debug Info. Base Address: $6F510000. Process Project13.exe (13088)
Module Load: urlmon.dll. No Debug Info. Base Address: $6CE50000. Process Project13.exe (13088)
Module Load: WINMM.dll. No Debug Info. Base Address: $72F20000. Process Project13.exe (13088)
Module Load: d3d9.dll. No Debug Info. Base Address: $68C10000. Process Project13.exe (13088)
Module Load: WINSPOOL.DRV. No Debug Info. Base Address: $6F280000. Process Project13.exe (13088)
Module Load: iertutil.dll. No Debug Info. Base Address: $6CC30000. Process Project13.exe (13088)
Module Load: WINMMBASE.dll. No Debug Info. Base Address: $72A10000. Process Project13.exe (13088)
Module Load: WINMMBASE.dll. No Debug Info. Base Address: $001D0000. Process Project13.exe (13088)
Module Unload: WINMMBASE.dll. Process Project13.exe (13088)
Module Load: WINMMBASE.dll. No Debug Info. Base Address: $001D0000. Process Project13.exe (13088)
Module Unload: WINMMBASE.dll. Process Project13.exe (13088)
Module Load: dwmapi.dll. No Debug Info. Base Address: $6C320000. Process Project13.exe (13088)
Module Load: bcrypt.dll. No Debug Info. Base Address: $729E0000. Process Project13.exe (13088)
Module Load: IMM32.dll. No Debug Info. Base Address: $76370000. Process Project13.exe (13088)
Module Load: UxTheme.dll. No Debug Info. Base Address: $6C2A0000. Process Project13.exe (13088)
Module Load: MSCTF.dll. No Debug Info. Base Address: $761C0000. Process Project13.exe (13088)
Module Load: gdiplus.dll. No Debug Info. Base Address: $6BFA0000. Process Project13.exe (13088)
Thread Start: Thread ID: 2908. Process Project13.exe (13088)
Module Load: TextInputFramework.dll. No Debug Info. Base Address: $6F1E0000. Process Project13.exe (13088)
Module Load: CoreMessaging.dll. No Debug Info. Base Address: $6C8A0000. Process Project13.exe (13088)
Module Load: CoreUIComponents.dll. No Debug Info. Base Address: $6C930000. Process Project13.exe (13088)
Module Load: NTMARTA.dll. No Debug Info. Base Address: $71F60000. Process Project13.exe (13088)
Module Load: WinTypes.dll. No Debug Info. Base Address: $70CF0000. Process Project13.exe (13088)
Module Load: USERMGRCLI.dll. No Debug Info. Base Address: $70C00000. Process Project13.exe (13088)
Thread Start: Thread ID: 14704. Process Project13.exe (13088)
Thread Start: Thread ID: 11932. Process Project13.exe (13088)
Thread Start: Thread ID: 12476. Process Project13.exe (13088)
Module Load: CLBCatQ.DLL. No Debug Info. Base Address: $74210000. Process Project13.exe (13088)
Module Load: DataExchange.dll. No Debug Info. Base Address: $5B340000. Process Project13.exe (13088)
Module Load: d3d11.dll. No Debug Info. Base Address: $625F0000. Process Project13.exe (13088)
Module Load: dcomp.dll. No Debug Info. Base Address: $5B250000. Process Project13.exe (13088)
Module Load: dxgi.dll. No Debug Info. Base Address: $62850000. Process Project13.exe (13088)
Module Load: twinapi.appcore.dll. No Debug Info. Base Address: $6F790000. Process Project13.exe (13088)
Module Load: d3d10_1.dll. No Debug Info. Base Address: $6B4A0000. Process Project13.exe (13088)
Module Load: d3d10_1core.dll. No Debug Info. Base Address: $69450000. Process Project13.exe (13088)
Module Unload: d3d10_1core.dll. Process Project13.exe (13088)
Module Unload: d3d10_1.dll. Process Project13.exe (13088)
Module Load: d3d10_1.dll. No Debug Info. Base Address: $6B4A0000. Process Project13.exe (13088)
Module Load: d3d10_1core.dll. No Debug Info. Base Address: $69450000. Process Project13.exe (13088)
Module Load: ResourcePolicyClient.dll. No Debug Info. Base Address: $6D230000. Process Project13.exe (13088)
Module Unload: ResourcePolicyClient.dll. Process Project13.exe (13088)
Module Load: igd10iumd32.dll. No Debug Info. Base Address: $5C3A0000. Process Project13.exe (13088)
Module Load: ncrypt.dll. No Debug Info. Base Address: $6B860000. Process Project13.exe (13088)
Module Load: NTASN1.dll. No Debug Info. Base Address: $6B830000. Process Project13.exe (13088)
Module Load: igdusc32.dll. No Debug Info. Base Address: $5ECD0000. Process Project13.exe (13088)
Module Unload: igdusc32.dll. Process Project13.exe (13088)
Module Unload: NTASN1.dll. Process Project13.exe (13088)
Module Unload: ncrypt.dll. Process Project13.exe (13088)
Module Unload: igd10iumd32.dll. Process Project13.exe (13088)
Module Load: igd10iumd32.dll. No Debug Info. Base Address: $5C3A0000. Process Project13.exe (13088)
Module Load: ncrypt.dll. No Debug Info. Base Address: $6B860000. Process Project13.exe (13088)
Module Load: NTASN1.dll. No Debug Info. Base Address: $6B830000. Process Project13.exe (13088)
Module Load: igdusc32.dll. No Debug Info. Base Address: $5ECD0000. Process Project13.exe (13088)
Module Load: d2d1.dll. No Debug Info. Base Address: $51D40000. Process Project13.exe (13088)
Module Load: CRYPT32.dll. No Debug Info. Base Address: $73EE0000. Process Project13.exe (13088)
Module Load: MSASN1.dll. No Debug Info. Base Address: $74390000. Process Project13.exe (13088)
Module Load: DWrite.dll. No Debug Info. Base Address: $51AF0000. Process Project13.exe (13088)
Module Load: WindowsCodecs.dll. No Debug Info. Base Address: $699C0000. Process Project13.exe (13088)

Notice, again, this is not specific to Delphi 10.2 Tokyo or Delphi 10.1 Berlin, but the same applies to the XE series and even classic versions of the product. The issue is caused by a change at the operating system level.

If you are a developer using RAD Studio, we recommend holding off moving to Windows 10 Creators Update on your developer machines, but this is clearly not a solution, also also prevents you from experimenting with the latest version of Windows.

First Solution: Embarcadero to Fix the Linker

Given the issue is how runtime packages are managed by the operating system, the ultimate solutions can come only from two player: Embarcadero or Microsoft. In fact, it is coming from both sides.

On the Embarcadero side, our R&D team has worked on changing the linker in 10.2 Tokyo, so that it produces a single import table with all required entries. The problem is if we just release a new linker, all existing package libraries will still misbehave. So we need to update a fairly large portion of the product, something more commonly done in an Update (or new Release) than via a hot fix. This is by no mean a final decision and R&D and PM are weighing in the alternatives. Now, what about older version of Delphi? Given the effect on packages (from us and third parties) all requiring to be recompiled, this is a fairly difficult scenario to address for past versions of RAD Studio.

Second Solution: Microsoft to Fix the Loader

The second solution would be to Microsoft to address the issue wih the loaded, keep the optimized parallel loading but taking into account the scenario of Delphi packages (which, in fact, happens also with a handful of platform libraries, even if to a more limited extent). Now, we are very happy to share the fact that we have engaged with Microsoft on the issue and they have been very fast to tackle it. The latest 16215 "Insider Build" of Windows 10 Fall Creators Update (https://blogs.windows.com/windowsexperience/2017/06/08/announcing-windows-10-insider-preview-build-16215-pc-build-15222-mobile) addresses the issue. As you can see, using the RTM version of 10.2 Tokyo the FMX library is loaded twice. Still not exactly as it used to work, but not really causing any actual problem:

This is the complete event log as you start debugging a Windows FireMonkey application with runtime packages on build 16215. Lines related with Delphi packages are in bold:

Thread Start: Thread ID: 208. Process Project3.exe (6184)
Process Start: C:\Users\Marco\Documents\Embarcadero\Studio\Projects\Win32\Debug\Project3.exe. Base Address: $00400000. Process Project3.exe (6184)
Module Load: Project3.exe. Has Debug Info. Base Address: $00400000. Process Project3.exe (6184)
Module Load: ntdll.dll. No Debug Info. Base Address: $76FA0000. Process Project3.exe (6184)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $74360000. Process Project3.exe (6184)
Module Unload: KERNEL32.dll. Process Project3.exe (6184)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $74360000. Process Project3.exe (6184)
Module Load: KERNELBASE.dll. No Debug Info. Base Address: $76DD0000. Process Project3.exe (6184)
Module Load: rtl250.bpl. Has Debug Info. Base Address: $50050000. Process Project3.exe (6184)
Module Load: OLEAUT32.dll. No Debug Info. Base Address: $74EA0000. Process Project3.exe (6184)
Module Load: msvcp_win.dll. No Debug Info. Base Address: $76C20000. Process Project3.exe (6184)
Module Load: ucrtbase.dll. No Debug Info. Base Address: $76B00000. Process Project3.exe (6184)
Module Load: combase.dll. No Debug Info. Base Address: $76680000. Process Project3.exe (6184)
Module Load: RPCRT4.dll. No Debug Info. Base Address: $74F40000. Process Project3.exe (6184)
Module Load: SspiCli.dll. No Debug Info. Base Address: $739F0000. Process Project3.exe (6184)
Module Load: CRYPTBASE.dll. No Debug Info. Base Address: $739E0000. Process Project3.exe (6184)
Module Load: bcryptPrimitives.dll. No Debug Info. Base Address: $74580000. Process Project3.exe (6184)
Module Load: SECHOST.dll. No Debug Info. Base Address: $746A0000. Process Project3.exe (6184)
Module Load: ADVAPI32.dll. No Debug Info. Base Address: $76D50000. Process Project3.exe (6184)
Module Load: msvcrt.dll. No Debug Info. Base Address: $73D00000. Process Project3.exe (6184)
Module Load: USER32.dll. No Debug Info. Base Address: $764E0000. Process Project3.exe (6184)
Module Load: win32u.dll. No Debug Info. Base Address: $73A10000. Process Project3.exe (6184)
Module Load: GDI32.dll. No Debug Info. Base Address: $74660000. Process Project3.exe (6184)
Module Load: gdi32full.dll. No Debug Info. Base Address: $73AC0000. Process Project3.exe (6184)
Module Load: imagehlp.dll. No Debug Info. Base Address: $745E0000. Process Project3.exe (6184)
Module Load: SHLWAPI.dll. No Debug Info. Base Address: $76CF0000. Process Project3.exe (6184)
Module Load: ole32.dll. No Debug Info. Base Address: $74480000. Process Project3.exe (6184)
Module Load: WS2_32.dll. No Debug Info. Base Address: $73C90000. Process Project3.exe (6184)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02B40000. Process Project3.exe (6184)
Module Unload: fmx250.bpl. Process Project3.exe (6184)
Module Load: VERSION.dll. No Debug Info. Base Address: $73850000. Process Project3.exe (6184)
Module Load: MPR.dll. No Debug Info. Base Address: $6FC30000. Process Project3.exe (6184)
Module Load: SHFOLDER.dll. No Debug Info. Base Address: $6FC60000. Process Project3.exe (6184)
Module Load: SHELL32.dll. No Debug Info. Base Address: $75100000. Process Project3.exe (6184)
Module Load: CFGMGR32.dll. No Debug Info. Base Address: $74CC0000. Process Project3.exe (6184)
Module Load: SHCORE.dll. No Debug Info. Base Address: $75010000. Process Project3.exe (6184)
Module Load: Windows.Storage.dll. No Debug Info. Base Address: $74700000. Process Project3.exe (6184)
Module Load: AppCore.dll. No Debug Info. Base Address: $746F0000. Process Project3.exe (6184)
Module Load: POWRPROF.dll. No Debug Info. Base Address: $74430000. Process Project3.exe (6184)
Module Load: profapi.dll. No Debug Info. Base Address: $76660000. Process Project3.exe (6184)
Module Load: NETAPI32.dll. No Debug Info. Base Address: $6EA80000. Process Project3.exe (6184)
Module Load: WINHTTP.dll. No Debug Info. Base Address: $70F70000. Process Project3.exe (6184)
Thread Start: Thread ID: 6828. Process Project3.exe (6184)
Module Load: WSOCK32.dll. No Debug Info. Base Address: $70D50000. Process Project3.exe (6184)
Module Load: OLEACC.dll. No Debug Info. Base Address: $6FB20000. Process Project3.exe (6184)
Module Load: OPENGL32.dll. No Debug Info. Base Address: $6C8D0000. Process Project3.exe (6184)
Thread Start: Thread ID: 6456. Process Project3.exe (6184)
Module Load: GLU32.dll. No Debug Info. Base Address: $6FAC0000. Process Project3.exe (6184)
Module Load: netutils.dll. No Debug Info. Base Address: $6E4A0000. Process Project3.exe (6184)
Module Load: fmx250.bpl. Has Debug Info. Base Address: $02C40000. Process Project3.exe (6184)
Module Load: COMDLG32.dll. No Debug Info. Base Address: $76A10000. Process Project3.exe (6184)
Module Load: COMCTL32.dll. No Debug Info. Base Address: $70D60000. Process Project3.exe (6184)
Module Load: urlmon.dll. No Debug Info. Base Address: $6FF00000. Process Project3.exe (6184)
Module Load: WINMM.dll. No Debug Info. Base Address: $6CEC0000. Process Project3.exe (6184)
Module Load: WINSPOOL.DRV. No Debug Info. Base Address: $6C860000. Process Project3.exe (6184)
Module Load: d3d9.dll. No Debug Info. Base Address: $6B960000. Process Project3.exe (6184)
Module Load: iertutil.dll. No Debug Info. Base Address: $6FCE0000. Process Project3.exe (6184)
Thread Start: Thread ID: 7136. Process Project3.exe (6184)
Module Load: WINMMBASE.dll. No Debug Info. Base Address: $6CE90000. Process Project3.exe (6184)
Module Load: dwmapi.dll. No Debug Info. Base Address: $6F4C0000. Process Project3.exe (6184)
Module Load: bcrypt.dll. No Debug Info. Base Address: $71C50000. Process Project3.exe (6184)
Module Load: IMM32.dll. No Debug Info. Base Address: $74E70000. Process Project3.exe (6184)
Thread Start: Thread ID: 4232. Process Project3.exe (6184)
Module Load: UxTheme.dll. No Debug Info. Base Address: $70620000. Process Project3.exe (6184)
Module Load: MSCTF.dll. No Debug Info. Base Address: $768C0000. Process Project3.exe (6184)
Module Load: gdiplus.dll. No Debug Info. Base Address: $70830000. Process Project3.exe (6184)
Thread Start: Thread ID: 3124. Process Project3.exe (6184)
Module Load: TextInputFramework.dll. No Debug Info. Base Address: $6C7A0000. Process Project3.exe (6184)
Module Load: CoreUIComponents.dll. No Debug Info. Base Address: $6C570000. Process Project3.exe (6184)
Module Load: CoreMessaging.dll. No Debug Info. Base Address: $6C4D0000. Process Project3.exe (6184)
Module Load: NTMARTA.dll. No Debug Info. Base Address: $705F0000. Process Project3.exe (6184)
Module Load: WinTypes.dll. No Debug Info. Base Address: $6C400000. Process Project3.exe (6184)
Module Load: WinTypes.dll. No Debug Info. Base Address: $05960000. Process Project3.exe (6184)
Module Unload: WinTypes.dll. Process Project3.exe (6184)
Thread Start: Thread ID: 3616. Process Project3.exe (6184)
Thread Start: Thread ID: 5984. Process Project3.exe (6184)
Module Load: CLBCatQ.DLL. No Debug Info. Base Address: $73A30000. Process Project3.exe (6184)
Module Load: DataExchange.dll. No Debug Info. Base Address: $69B60000. Process Project3.exe (6184)
Module Load: d3d11.dll. No Debug Info. Base Address: $69910000. Process Project3.exe (6184)
Module Load: dcomp.dll. No Debug Info. Base Address: $69800000. Process Project3.exe (6184)
Module Load: dxgi.dll. No Debug Info. Base Address: $69770000. Process Project3.exe (6184)
Module Load: twinapi.appcore.dll. No Debug Info. Base Address: $6CBF0000. Process Project3.exe (6184)
Module Load: RMCLIENT.dll. No Debug Info. Base Address: $6CBD0000. Process Project3.exe (6184)
Module Load: d3d10_1.dll. No Debug Info. Base Address: $63B40000. Process Project3.exe (6184)
Module Load: d3d10_1core.dll. No Debug Info. Base Address: $63AE0000. Process Project3.exe (6184)
Module Unload: d3d10_1core.dll. Process Project3.exe (6184)
Module Unload: d3d10_1.dll. Process Project3.exe (6184)
Module Load: d3d10_1.dll. No Debug Info. Base Address: $63B40000. Process Project3.exe (6184)
Module Load: d3d10_1core.dll. No Debug Info. Base Address: $63AE0000. Process Project3.exe (6184)
Module Load: ResourcePolicyClient.dll. No Debug Info. Base Address: $63A40000. Process Project3.exe (6184)
Module Unload: ResourcePolicyClient.dll. Process Project3.exe (6184)
Module Load: vm3dum10.exe. No Debug Info. Base Address: $63AA0000. Process Project3.exe (6184)
Module Unload: vm3dum10.exe. Process Project3.exe (6184)
Module Load: vm3dum10.exe. No Debug Info. Base Address: $63AA0000. Process Project3.exe (6184)
Module Unload: vm3dum10.exe. Process Project3.exe (6184)
Module Load: vm3dum10.exe. No Debug Info. Base Address: $63AA0000. Process Project3.exe (6184)
Module Unload: vm3dum10.exe. Process Project3.exe (6184)
Module Load: vm3dum10.exe. No Debug Info. Base Address: $63AA0000. Process Project3.exe (6184)
Module Load: d2d1.dll. No Debug Info. Base Address: $65120000. Process Project3.exe (6184)
Module Load: CRYPT32.dll. No Debug Info. Base Address: $73DC0000. Process Project3.exe (6184)
Module Load: MSASN1.dll. No Debug Info. Base Address: $75000000. Process Project3.exe (6184)
Module Load: DWrite.dll. No Debug Info. Base Address: $64EA0000. Process Project3.exe (6184)
Module Load: WindowsCodecs.dll. No Debug Info. Base Address: $6C290000. Process Project3.exe (6184)

Perfect solution, right? Well, it does fix the issue for current and old versions of Delphi, but unfortunately not immediately. It is true Microsoft fixed the problem, but if the solution will show only in the next major release of the operating system, still several months away (Fall Creators Update), what happens to developers and users on Creators Update? We still hope and have been asking Microsoft for a fix also for the current version of Windows, and you can certainly join us in this request.

Some Temporary Workarounds

Given the two solutions above are coming but don't address the issue immediately and for all developers, it is important to focus also on a few available workarounds.

A first one is for debugging. Given the issue happens when loading the application, running it standalone and later attaching the debugger to it seems to work for most developers. Clearly, it is an annoyance, but clearly much better than waiting a lot of time or see the debugger get stuck.

A second workaround (for end users) is to consider one of the tools that fix-up and cleanup PE executables, including reorganizing the import/export tables. There are many such tools. One of them is http://www.ntcore.com/exsuite.php.

There are of course other more extreme options, like staying on Windows 10 Anniversary edition, jumping to the latest Insider release or moving from the use of runtime packages to releasing a single executable.

Conclusion

We are working on releasing our linker solution for the issue, we'll keep pushing Microsoft for a broad and more immediate fix, and we are also evaluating alternative workarounds for the short term. Stay tuned for more information.

posted by marcocantu @ 9:04AM | 30 Comments [0 Pending]

Can we vote

> We still hope and have been asking Microsoft for a
fix also for the current version of Windows, and you
can certainly join us in this request.

Any link where we can vote for that?

Comment by Yeray on June 12, 11:02

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Yeray,

> Any link where we can vote for that?

Not that I know...

Comment by Marco Cantu [http://twitter.com/marcocantu] on June 12, 12:44

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

This is a rather devastating problem for me.
All my programs use runtime packages and ask all my customers 
not to update win10, will not be easy.
However this is not the only problem that afflicts Delphi on 
Win10, on XE3 I could not launch the program from inside the 
IDE because the system was blocking (I had to reset the pc). I 
learned that it was a problem that solved only by setting Delphi's 
affinity to a single processor, which was extremely uncomfortable 
and that lengthened the compilation times.
To solve I went to Seattle just to see that anyway the problem had 
not been solved. I do not know if the new releases have been fixed, 
I hope so, anyway, as I think many other developers, I can not 
change the development environment every year, this for various 
reasons first on all that I do not have the time. It would be nice for 
Embarcadero to release updates in some cases even for older 
versions.

Comment by Lorenzo Biondi on June 13, 06:40

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Lorenzo,

just to clarify. The issue is not with Windows 10 at large, only for 
Creators Update. In most cases customers are not affected in a big, 
way, only a limited slow down on start. The debugger is badly 
affected.

Just to be clear, this is not a bug in Delphi. Microsoft changes an 
operating system established behaviour (20+ years) and in fact they 
reverted the change and fixed it!

Comment by Marco Cantu [http://twitter.com/marcocantu] on June 13, 07:39

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Sorry Marco, I did not mean to say that this was a problem of 
Delphi, I expressed myself badly. It is clear that the problem in this 
case depends on Microsoft.

Comment by Lorenzo Biondi on June 13, 08:05

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Thank you Marco for sharing all the details of the
current situation.

The main problem is that we cannot force customer to
stay behind "Windows 10 Creators Update". Actually our
own internal Windows Update Service provide the
release to all our Windows 10 Workstations more than 1
month ago. For our internal development we do have
some workarounds. But the IT of the big customers will
not discuss. They ship/not ship what is delivered in
the main Microsoft weekly/monthly update cycles.

Still hope that Embarcadero can convince Microsoft to
ship an earlier official fix for the Loader.

Comment by Günther Schoch [http://gs-soft.com] on June 13, 09:48

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Marco Cantù wrote:
===== START OF QUOTE =====
Microsoft changes an operating system established behaviour (20+ 
years) and in fact they reverted the change and fixed it!
===== END OF QUOTE =====

Are you saying that Microsoft has finally fixed the problem, so we 
now have nothing to worry about?

Comment by Pasquale Esposito [http://www.espositosoftware.it] on June 13, 10:54

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Pasquale, 

> Are you saying that Microsoft has finally fixed the problem, so we 
now have nothing to worry about?

Yes and no. Microsoft fixed the problem but in the beta of the next 
version of Windows (Fall Creators Update), not in the current version 
(Creators Update).

Comment by Marco Cantu [http://twitter.com/marcocantu] on June 13, 12:40

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Hello,
i'd like to inform you, that i've installed 16215 build of Windows 
10 and the issue is fixed in the exe with runtime packages (IDE 
sometimes gets stuck while loading modules, but it's rather 
occasional situation)...but the issue remains the same if you try to 
debug dll (using "Host application" parameter) - i haven't 
succeeded neither once trying to run dll.

Is there possibility to some sort of solution in Delphi Seattle?

Regards, Jaroslav

Comment by Jaroslav Cap on June 13, 20:17

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 This is weird, I'm using a single EXE package (no
DLL) and with  "Enable Runtime Style" in the option
(Delphi Xe4)
not selected, I get corrupted DateTimePicker rendition
in all my applications.  If I "enable" the Runtime
Style, then the DateTime Picker is correct but all my
color selection and text color are disturbed.  This
came about with Windows 10 Creators and I (plus a few
more) have posted the same issue on the Microsoft
Developer network forum.
Is it a known issue to Embarcadero?

Comment by Robert Côté [http://www.minidcc.com] on June 15, 20:26

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Hello Marco

There is a rather controversy feedback concerning the
BugFix within windows 10 build 16215. It would be very
helpful if you could continue to openly post the
current findings and status. That would give us the
necessary confidence. As well the QA process of
EMBT/Idera should think about implementing a BETA
testing of the new Windows versions including exactly
such heavy debugging scenarios. 

regards, Günther

Comment by Günther Schoch [http://gs-soft.com] on June 16, 08:53

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Robert, 

the DateTimePicker issue is a separate one and I've been told this was 
fix by the "2017-06 Update for Windows 10 9KB4022405)" of 
Creators Update. it was a Windows bug -- totally separate from what 
discussed here.

Gunther, 
you are right we should have found the issue sooner, but still the only 
real solution would have been to report it earlier to Microsoft. We 
have seen the issue fixed on all updated machines and Microsoft 
informed us of the fix.

Comment by Marco Cantu [http://twitter.com/marcocantu] on June 16, 13:54

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Marco said:
"We 
have seen the issue fixed on all updated machines and Microsoft 
informed us of the fix." 

Can you send us the URL to microsoft issue? I'd like to get the update 
ASAP.

Comment by Jaroslav Cap on June 19, 07:39

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 I'm testing the latest insider build but the issue is still present. The bpl 
are loaded and unloaded lot of times and sometimes the ide hang or 
crash with internal error. Are you sure that the old loading mode has 
been reintroduced? 
Thanks 
Pierangelo

Comment by Pierangelo on August 4, 06:37

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Yet another pain in the wrong place  - Microsoft are the biggest 
software company in the world and yet they manage to wreck havoc 
at every step - just goes to show that the more money you throw at a 
shit maze the more shit your can expect. On the flip side Embers, I 
pay you an annual fee to sort this shit out so get on with it.

Comment by Peter [http://www.qsys.co.uk] on August 5, 23:03

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Credit where credit due.  Well done in getting the issue sorted.   
https://community.embarcadero.com/article/16556-rad-studio-10-2-1-
released-today

Comment by Peter Edwards [http://www.Qsys.co.uk] on August 8, 22:52

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Don't expect Microsoft to fix loader. 

Probably better solution is not to use BPL files at 
all. I was used them in Delphi 4 (or 5?) and found 
that for debug/development works well. But fail 
spectacular with creating installers. That's why we 
never used them for real apps.

Comment by Peter Nikolow [http://www.mobiliodevelopment.com] on August 14, 17:15

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 > on XE3 I could not launch the program from inside the 
IDE because the system was blocking (I had to reset the pc)

Weird. XE2 works okay on Win10

Tried Delphi 10.1 (free starter) - seems working too

Comment by Arioch on August 17, 15:46

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Windows 10 Fall Creators Update didn't solved for me the 
Database Desktop loading problem. : //

Comment by agyas on October 19, 13:48

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Agyas, not sure because I installed the final version of Fall Creators 
Update today and I see one or two uploads/downloads of BPL, not 
the dozen that used to be there before. You'd have to provide more 
specific information: which version of Delphi, what are you 
observing, which version of Windows 10.... etc etc. but not here, 
better in Quality Portal....

Comment by Marco Cantu [http://www.marcocantu.com] on October 19, 14:42

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Same for me here, Fall update did not solve the issue, debugger 
hangs the IDE most of the time when launching. Events log shows 
dll are loaded multiple times. I have RAD Studio 10.2 Version 
25.0.27659.1188 with all patches applyed. killing the debugged  
Application with task manager frees the IDE.

here is the log after the kill
Début du Thread : ID du thread : 8736. Processus SQLtool.exe 
(6364)
Début du processus : C:\chris\query\SQLtool.exe. Adresse de base 
: $00400000. Processus SQLtool.exe (6364)
Chargement du module : SQLtool.exe. Contient des infos de 
débogage. Adresse de base : $00400000. Processus SQLtool.exe 
(6364)
Chargement du module : ntdll.dll. Pas d'informations de débogage. 
Adresse de base : $773C0000. Processus SQLtool.exe (6364)
Chargement du module : KERNEL32.dll. Pas d'informations de 
débogage. Adresse de base : $758E0000. Processus SQLtool.exe 
(6364)
Chargement du module : KERNELBASE.dll. Pas d'informations 
de débogage. Adresse de base : $771E0000. Processus 
SQLtool.exe (6364)
Début du Thread : ID du thread : 3192. Processus SQLtool.exe 
(6364)
Début du Thread : ID du thread : 9640. Processus SQLtool.exe 
(6364)
Chargement du module : SHLWAPI.dll. Pas d'informations de 
débogage. Adresse de base : $76910000. Processus SQLtool.exe 
(6364)
Chargement du module : msvcrt.dll. Pas d'informations de 
débogage. Adresse de base : $76590000. Processus SQLtool.exe 
(6364)
Chargement du module : WINMM.dll. Pas d'informations de 
débogage. Adresse de base : $73520000. Processus SQLtool.exe 
(6364)
Début du Thread : ID du thread : 7840. Processus SQLtool.exe 
(6364)
Chargement du module : OLEACC.dll. Pas d'informations de 
débogage. Adresse de base : $6A590000. Processus SQLtool.exe 
(6364)
Chargement du module : combase.dll. Pas d'informations de 
débogage. Adresse de base : $766C0000. Processus SQLtool.exe 
(6364)
Chargement du module : WINMMBASE.dll. Pas d'informations de 
débogage. Adresse de base : $726F0000. Processus SQLtool.exe 
(6364)
Chargement du module : ucrtbase.dll. Pas d'informations de 
débogage. Adresse de base : $75360000. Processus SQLtool.exe 
(6364)
Chargement du module : ucrtbase.dll. Pas d'informations de 
débogage. Adresse de base : $03530000. Processus SQLtool.exe 
(6364)
Déchargement du module : ucrtbase.dll. Processus SQLtool.exe 
(6364)
Chargement du module : WINMMBASE.dll. Pas d'informations de 
débogage. Adresse de base : $03200000. Processus SQLtool.exe 
(6364)
Déchargement du module : WINMMBASE.dll. Processus 
SQLtool.exe (6364)
Chargement du module : CFGMGR32.dll. Pas d'informations de 
débogage. Adresse de base : $771A0000. Processus SQLtool.exe 
(6364)
Chargement du module : RPCRT4.dll. Pas d'informations de 
débogage. Adresse de base : $03530000. Processus SQLtool.exe 
(6364)
Sortie du Thread : ID du thread : 7840. Processus SQLtool.exe 
(6364)
Sortie du Thread : ID du thread : 3192. Processus SQLtool.exe 
(6364)
Chargement du module : RPCRT4.dll. Pas d'informations de 
débogage. Adresse de base : $75A00000. Processus SQLtool.exe 
(6364)
Sortie du Thread : ID du thread : 8736. Processus SQLtool.exe 
(6364)

Comment by Chris on October 20, 12:25

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

At least one ther erson is reporting the issue here (see post from 
18/10/217)
 https://forums.embarcadero.com/thread.jspa?threadID=249463

For me problem is even worse with W10 fall update. No the 
debugger freezes 9/10 times.

My invetigations show that changing bds.exe affinity to 1 
processor instead of all 8 solves the problem.

But I won't open a QC because I don't have enought clues and 
"Guru meditation" as a proble description will get my QC closed 
as "not reproductible" quicker than you can ansxer this post :).

But I can offer you free direct access to my brand new tokyo 
machine with gotoassist (thru www.fastsupport.com)  if we can 
setup a meeting date . This way you can experience the problem 
and open a QC signed marcocantu that will get attention.

Why people do not complain more is a mistery, We have 7 new 
machines with W10+tokyo and all 7 exhibit the problem. 

Maybe our Machines are too fast with 8 cores and 2 SSD in RAID 
?

Aside from this, what's also strange is that 2426282 lines of code 
still takes 30s to full build on SSD while the old machine with 2 
HDD raid takes 32s. Benchmarks shows the SSD outperforms the 
HDD by factor 1000 in reading and factor 500 in write but we only 
get 2 seconds faster than XE2 on the older machine. Even the cpu 
is faster on the new machine, but no benefit. Anyway, I disgress 
the speed is still good even if not better, the main problem is still 
the debugger freezing issue.

I think this blog is still te best place to provide feeback until we 
understand what's going on. I don't want to open a QC with just a 
theory and vague explanations. Maybe it's not exactly the same 
issue as the dll loading.

Comment by Chris on October 24, 15:25

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Hello Marco,

Finaly I have a clue ! It will please you :)
I have trimmed down my debugger freezing problem.

Requirements to reproduce :
* Affinity set to multiple cores
* Compile in 32 bits debug mode (no problem in 64 bits)
* Have F-Secure Client Security Premium 12.31 build 105
* Have F-Secure FSGKHS service active

But why is fsecure blocking the 32 bit debugger in multicore ? I 
cannot explain because I have no understanding of what happens 
internally ... and it will be super difficult for me to explain this to 
fsecure ... even more than in QC, because they probably don't have 
delphi to reproduce the issue.

Problem, Fall update made this much much much worse.

Any toughts to comfort me ?  

Changing the antivirus is not an option, it's a corporate version and 
I do not have the choice.

Comment by Chris on October 27, 14:53

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 Hello Chris

We have find the solution for Fsecure. We have excluded bds.exe in 
f-secure antivirus processus. It works good now

Comment by Calou on March 14, 11:12

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

RAD 10.2 Update 3

Been using this with Windows 10 1703/1709 and debug load times 
were fine.

Recently updated to Windows 1803 and the slow debug load times are 
back over 2 mins to load our application. Without the debugger < 15 
secs.

Anyone else experiencing this?

Comment by Rob on July 6, 07:59

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Hello,

It has been extremely unpleasant the time for compilation of 
executable.

Details:
-Delphi Berlin Update 1;
-Antivirus is completely disabled;
-Installed IDE Fix and FastDCC64 which theoretically aids in 
related problems;
-Windows 10 updated with update 1803
- In Tools Options -> Environment Options -> Delphi Options -> 
Library, I added in Library Path the complete path of DCUs;
-In Browsing Path too;

Very, very unproductive.
Please, if anyone has more information or suggestions thank you.

Marcos

Comment by Marcos on July 17, 13:01

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

What might help and solved my issues during debugging
was to set additonal compiler options after installing
the IDE Fix Pack. I am using Delphi XE2. You can get
the fixpack from
http://www.delphifeeds.com/go/s/143779 for your
specific version.

Under Project -> Options -> Delphi Compiler ->
Compiling -> Additional options to pass to the compiler

you have to add the following options: "-x-ff -x-fdi
-x-fvs -x-fpr". Don't forget to save the options set
somewhere and set a reference (e.g. click "save", save
the file and apply afterwards with setting the file as
a reference). A more detailed description about
setting this options can either be found within the
Readme.txt of the Fixpack or here:
http://www.delphifeeds.com/go/s/143024

I hope this will help you too, as I have been
searching for a solution regarding this problem for
about 2 weeks.

Comment by Matthias on November 22, 09:51

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The problem is back in 2020 (Windows 10 version 1903).
Fortunately (as Matthias has already noticed) Andy's IDE Fix Pack 
(version 6.4.4) fixes it for many versions of Delphi (including XE6 
we're working in).

Comment by Denis Zaytsev on January 30, 07:43

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

I wonder if the problem I'm experiencing is the same problem, W10, v1909, Delphi 10.4 64 bit, it's just too slow.

https://community.idera.com/developer-tools/general-development/f/rad-studio-general/73218/starting-delphi-10-4-64-bit-debugging-is-very-slow

Comment by Martijn Tonies on August 27, 19:21

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

 I can not start RAD Studio 10,
It stopped at splash screen forever,
how can I fix it ?

Thanks

Comment by Rick on March 25, 23:35

Marco Tech Blog

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Core Issue: Optimized DLL Loading

First Solution: Embarcadero to Fix the Linker

Second Solution: Microsoft to Fix the Loader

Some Temporary Workarounds

Conclusion

30 Comments

Can we vote

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

The Issue with Delphi Runtime Packages and Windows 10 Creators Update

Post Your Comment