DataGrid Crashes when running under .Net 4.0 - Extremely urgent

Hi Jason,

We have a problem with the datagrid under .Net4.0

1) Make sure your system only has .Net 4.0 installed

2) Run you Sample Explorer

3) Go to any DataGrid sample, it crashes.

We track back to the nightly builds, It has problem since March 24, 2016 nightly builds.

It works under .Net 4.5.1, but not under .Net 4.0

Please advise or fix them asap!!!!

By the way, We have to make it work under .Net 4.0.

Also Feb. 02, 2016 nightly builds are OK under .Net 4.0.

We also notice that when we install the software, it changes to Ragon between these 2 nightly build, thought this might be helpful.

Thanks, Gordon

Hi Gordon,

We're currently working on a couple of large releases over the next half week, so don't have time to downgrade any systems to only have .NET 4.0 installed. Would you be able to send more information about the crash, ideally exception information containing a stack trace, then I can compare that to any changes made around March.

-Jason Fauchelle

Hi Jason,

I would say we are very disappointed about the answer. I could not imagine that you do not have a test machine with only .Net4.0 installed. Even you make a change to fix this problem how would you know the problem is fixed if you even don't have a system to test on?

Every time we download the build from you, we have to spend 2 days to test if it is working, so we have been your QA for a long period of time.

And also, because of this, we have to postpone the release of our products.

Enough of this, the following are the information we get:

The trace for the initial crash window is:

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: sampleexplorer.exe
  Problem Signature 02: 7.0.0.0
  Problem Signature 03: 56f39fbe
  Problem Signature 04: PresentationFramework
  Problem Signature 05: 4.0.0.0
  Problem Signature 06: 4d64c9e2
  Problem Signature 07: 31ea
  Problem Signature 08: 32
  Problem Signature 09: System.InvalidOperationException
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1: 432b
  Additional Information 2: 432bf89a15af373dc7d138745ae20d90
  Additional Information 3: ede8
  Additional Information 4: ede8d409ab2cc38e3f9d99e1f0663f42

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

The debug information is:

Specified element is already the logical child of another element. Disconnect it first.   


   at System.Windows.FrameworkContentElement.ChangeLogicalParent(DependencyObject newParent)
   at System.Windows.FrameworkElement.AddLogicalChild(Object child)
   at System.Windows.Controls.ContentControl.OnContentChanged(Object oldContent, Object newContent)
   at System.Windows.Controls.ContentControl.OnContentChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
   at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
   at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
   at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
   at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
   at Mindscape.WpfElements.WpfDataGrid.DataGridRowPanel.PrepareContainer(DependencyObject element, Object item)
   at Mindscape.WpfElements.WpfDataGrid.DataGridRowPanel.GetContainer(Object item)
   at Mindscape.WpfElements.WpfDataGrid.DataGridRowPanel.FillItems(Int32 startIndex, Int32 maxCount, ItemCollection items, HashSet`1 nextCache, Double availableWidth, Size& stackDesiredSize)
   at Mindscape.WpfElements.WpfDataGrid.DataGridRowPanel.MeasureOverride(Size availableSize)
   at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
   at System.Windows.UIElement.Measure(Size availableSize)
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at SampleExplorer.App.Main()

The screen shot for the initial crash window is: DataGridCrashNET40FromSystem.JPG

The screenshot for the debuging window is: DataGridCrashNET40.JPG

We also hook up the source code and the screen shot for the place crashed in your code is: DataGridCrashInCode.jpg

Please test on your own system when you fix the problem.

We really need the fix as soon as possible!!!

Thanks, Gordon

By the way, you can only use Visual Studio 2010, for .Net4, other version of visual studio will install higher dot net version.

Gordon

Hi Gordon,

Just stepping in here. Understand you're unhappy. We will look into this, but it will take time unfortunately.

We no longer test against .NET 4 as Microsoft has also stopped supporting it. We don't support versions not supported by Microsoft.

The best solution (and correct solution) is to have your customers should upgrade to a supported version of .NET. It is free, and will ensure they get important framework updates.

You can read about the end of support for .NET 4, 4.5 and 4.5.1, which have all ceased being supported, here: https://support.microsoft.com/en-nz/lifecycle?p1=14380 (with more details here: https://support.microsoft.com/en-nz/lifecycle#gp/FrameworkFAQ )

As Jason mentioned, we will investigate this and see if there is a simple resolution, but we will need to take the time to set up an environment more than half a decade out of date to see what the issue is and patch it. This won't happen until late next week at the earliest.

Jason will update the thread once he's had an opportunity to investigate further and find the cause.

Kind regards,

John-Daniel Trask

Hi John and Jason

Since we past the release targeting date, and we cannot wait for the updates from you and another round of test.

I guess we have to force our client to install .Net 4.5.1 or newer.

Unless others have the request, you don't need to make fixes on this one for us.

Thanks, Gordon