Home Stackoverflow Exception with Delphi COM Interop and WPF after Windows Update
Reply: 0

Stackoverflow Exception with Delphi COM Interop and WPF after Windows Update

user2432
1#
user2432 Published in May 26, 2018, 7:47 am

we have issues with Windows 10 Updates (KB4041676, KB4041691) and our applications. Hopefully we'll find someone who can help.

The applications are Delphi 7 32 bit with an COM Interop .net part to connect to a service over WCF. When the KBs installed the application crashes with the following procdump output directly after start:

[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C0000091.FLOAT_OVERFLOW
[14:37:21] Exception: C00000FD.STACK_OVERFLOW

I have prepared a minimal sample. First .net dll Classes:

[ComVisible(true)]
[Guid("5725C8DE-B28F-4A82-BE75-E85EC1832AAA")]
public interface IMyNetComConnector
{
    void DoIt(string test);
}

[ClassInterface(ClassInterfaceType.None)]
[ComSourceInterfaces(typeof(IMyNetComConnector))]
[ComVisible(true)]
[Guid("5725C8DE-B28F-4A82-BE75-E85EC1832AAB")]
public class MyNetComConnector : IMyNetComConnector
{
    private ContentControl c;
    public void DoIt(string test)
    {
        c = new ContentControl();
        c.Content = "";
    }
}

We need the ContentControl for some ViewModels with inheritance, so in our code the error happens when we create these viewmodels.

In Delphi 7 i imported an ActiveX-Control in a vcl formular application and used it:

program Project3;

uses
  Forms, ActiveX,
  Unit2 in 'Unit2.pas' {Form2},
  MyNetComComponent_TLB in 'D:\MyNetComComponent_TLB.pas';

{$R *.res}
  var
  connector :  TMyNetComConnector;
begin
  CoInitialize(nil);
  connector := TMyNetComConnector.Create(nil);

  connector.Connect();
  connector.DoIt('test');
  Application.Initialize;
  Application.MainFormOnTaskbar := True;
  Application.CreateForm(TForm2, Form2);
  Application.Run;
end.

The posted code example above running in our application fine for over 4 years on Windows 7 and Windows 10 without the named KBs.

Is the root cause a change in the wpf initialization or .net framework bug or are there any policies which are active and enabled in the kbs?

Thanks in advance

You need to login account before you can post.

About| Privacy statement| Terms of Service| Advertising| Contact us| Help| Sitemap|
Processed in 0.309468 second(s) , Gzip On .

© 2016 Powered by mzan.com design MATCHINFO