Error and crashing of application after Windows 10 1903 Update

Stephan Edwards posted over 5 years ago

I am looking for some help determining an error we are having. We are having a problem with our application crashing after a user updates to Windows 10 1903. We are currently on Infragistics version 17.2. It's only happening in one area of our application and is random but the error is consistently hitting the same line of code.

We are able to reproduce the error, sometimes. Here’s the error we are getting when running a trace and when it does occur:

Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem

Additional Information: The runtime has encountered a fatal error. The address of the error was at 0xe8007240, on thread 0x34c8. The error code is 0xc0000005

Highlighted below in yellow is where the error is happening in the code

Private Sub LoadLayout(ByVal Ultragrid As Infragistics.Win.UltraWinGrid.UltraGrid, ByVal UltraGridID As Integer)
        Cursor.Current = Cursors.WaitCursor
        Ultragrid.SuspendLayout()
        Dim dCon As SqlClient.SqlConnection = New SqlClient.SqlConnection(ADONet)
        Dim dCom As SqlClient.SqlCommand = New SqlClient.SqlCommand("LoadGridLayout " & UltraGridID, dCon)
        dCon.Open()
        Dim isx As Boolean = False
        Dim dr As SqlClient.SqlDataReader
        dr = dCom.ExecuteReader
        If dr.Read Then
            Dim data() As Byte
            data = dr("Layout")
            Ultragrid.Layouts.Clear()
            Try
                If dr("IsXML") = 0 Then
                    Ultragrid.DisplayLayout.Load(New System.IO.MemoryStream(data), CType(Infragistics.Win.UltraWinGrid.PropertyCategories.ColumnFilters Or Infragistics.Win.UltraWinGrid.PropertyCategories.General Or Infragistics.Win.UltraWinGrid.PropertyCategories.Groups Or Infragistics.Win.UltraWinGrid.PropertyCategories.SortedColumns Or Infragistics.Win.UltraWinGrid.PropertyCategories.UnboundColumns Or Infragistics.Win.UltraWinGrid.PropertyCategories.AppearanceCollection Or Infragistics.Win.UltraWinGrid.PropertyCategories.Bands Or Infragistics.Win.UltraWinGrid.PropertyCategories.Summaries, Infragistics.Win.UltraWinGrid.PropertyCategories))
                Else
                    isx = True

                    Ultragrid.DisplayLayout.LoadFromXml(New System.IO.MemoryStream(data), CType(Infragistics.Win.UltraWinGrid.PropertyCategories.ColumnFilters Or Infragistics.Win.UltraWinGrid.PropertyCategories.General Or Infragistics.Win.UltraWinGrid.PropertyCategories.Groups Or Infragistics.Win.UltraWinGrid.PropertyCategories.SortedColumns Or Infragistics.Win.UltraWinGrid.PropertyCategories.UnboundColumns Or Infragistics.Win.UltraWinGrid.PropertyCategories.AppearanceCollection Or Infragistics.Win.UltraWinGrid.PropertyCategories.Bands Or Infragistics.Win.UltraWinGrid.PropertyCategories.Summaries, Infragistics.Win.UltraWinGrid.PropertyCategories))
                End If
            Catch
                'dr.Close()
                'dCom.CommandText = "Delete from GridLayout where Gridlayoutid = " & UltraGridID
                'dCom.ExecuteNonQuery()
            End Try
        End If
        dr.Close()
        Ultragrid.DisplayLayout.ResetAppearance()
        If isx = False Then
            Ultragrid.DisplayLayout.ResetValueLists()
        End If
        dCon.Close()
        'Ultragrid.DisplayLayout.Override.ActiveAppearancesEnabled = Infragistics.Win.DefaultableBoolean.False
        Cursor.Current = Cursors.Default
        gControl.CheckForCustomEditableFields()
        Ultragrid.ResumeLayout()
        Me.Close()
    End Sub

Parents

29105

Offline Michael DiFilippo posted over 5 years ago

Hello Edward,

I have the same 1903 update pending which I plan on installing today. In the meantime please provide a sample that reproduces the behavior. I noticed you included a few features such as column filters, groups, etc. Are these all required to cause the issue? If not, which grid features need to be saved, then loaded for the error to occur?
Cancel
Reply

Cancel
60

Offline Stephan Edwards posted over 5 years ago in reply to Michael DiFilippo

Hi Michael,

Thanks for the response. We found that the error was being caused by the file type icons for each row in the grid. It was designed so it would go to the local Windows machine and pull the icon for the file type based on whatever the file extension was. So, it was having to cross the application / system boundary and apparently 1903 doesn't like that.
Cancel
Reply

Cancel

Reply

469350

Offline Mike Saltzman posted over 5 years ago in reply to Stephan Edwards

Do you mean your application was getting the application icon, like for an exe or a file on the machine? Presumably, you have to use Windows API's for that. Maybe they changed the API in some way? Or perhaps they added security so your application requires full trust now, in order to use those APIs?

Edit: Oh, apparently, there's a method for it in the DotNet Framework.

https://docs.microsoft.com/en-us/dotnet/framework/winforms/advanced/how-to-extract-the-icon-associated-with-a-file-in-windows-forms
Cancel
Reply

Cancel

Children

No Data