Hi,
on some customer pcs the programm crashes with a standard windows error message when the user the clicks on the FieldChooser button.
Have you got a idea what can cause this behavior? We are using Release 12.1.
With kind regards
Lucas
The Windows error message:
Problemsignatur: Problemereignisname: APPCRASH Anwendungsname: PlugHost.exe Anwendungsversion: 1.14.10.1705 Anwendungszeitstempel: 58909e92 Fehlermodulname: StackHash_eec2 Fehlermodulversion: 0.0.0.0 Fehlermodulzeitstempel: 00000000 Ausnahmecode: c000041d Ausnahmeoffset: 74294f69 Betriebsystemversion: 6.1.7601.2.1.0.256.48 Gebietsschema-ID: 1031 Zusatzinformation 1: eec2 Zusatzinformation 2: eec21d1a65e580d17e077112173f6bfe Zusatzinformation 3: eb38 Zusatzinformation 4: eb38522c007d97680c0e4a36aa16a7a1
Hello,
Thank you for contacting Infragistics. I've tested the field chooser functionality in 12.1 in Windows 10 64-bit and was not able to reproduce any unexpected behavior. I've attached my sample for your reference. Please test it accordingly and clarify the steps on how to reproduce the behavior.
Please note, version 12.1 is retired and no longer maintained.
Let me know if you have any questions.
Hello Michael,
the crash only occurs on a few customer pcs. In our test environment we also can't reproduce this behavior. Your sample also crashes with following message:
Beschreibung:
Stopped working
Problemsignatur:
Problemereignisname: CLR20r3
Problemsignatur 01: feldauswahltest.exe
Problemsignatur 02: 1.0.0.0
Problemsignatur 03: 59709e20
Problemsignatur 04: WindowsBase
Problemsignatur 05: 3.0.0.0
Problemsignatur 06: 58d92480
Problemsignatur 07: 361
Problemsignatur 08: 9
Problemsignatur 09: System.ComponentModel.Win32
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
We are using release 12.1 because is the last release for .net 3.5.
Kind regards
Hello Lucas,
I was not able to reproduce any crash in 12.1 build (2314 last service release) in CLR .netL 3.5.
Which build more specifically (four digits trailing the version) are you using? Let me know if you have any quesitons regarding this matter.
we are using Release 12.1.20121.1010. As already mentioned we also can't reproduce this beahavior in our test enviroment. Can you tell me what happens wenn the Fieldchooser button is pressed? Do you use WinAPI calls?
Thank you for following up. Our team would have to investigate at our source code to determine the root cause. I don't know off hand for sure what is performed related to the exception. Do you have any specific questions?
yes my first question is as mentioned above if some WinAPI calls are perfomed when the button is clicked. Are they some other routines that could provoke this behavior?
Thank you for following up. But unfortunately no, I am not aware of anything that would provoke this issue. Please provide a recording of the issue occurring and the machine details. eg. Windows version etc.