Watch, Follow, &
Connect with Us

Welcome, Guest
Guest Settings
Help

Thread: Delphi 2007 Win32 .exe closes with AV (Access Violation) in uiautomation.dl


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 1 - Last Post: Mar 12, 2017 3:26 AM Last Post By: Jony Bassan
Brian Clingan

Posts: 1
Registered: 8/12/11
Delphi 2007 Win32 .exe closes with AV (Access Violation) in uiautomation.dl  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 22, 2017 9:35 PM
Currently, we are seeing an AV in UIAutomationCore.dll when a Win32 .exe application closes. This is a software product that has been running on Windows XP, Windows 7 and now running it on Windows 10. Have only seen this issue on Windows 10.

Note: The Win32 applications are built using Delphi IDE 2007

Application Error: Exception EAccessViolation in module uiautomationcore.dll at 0006AOC9.

Cases:
1. Win32 App 1: In the first case every time the Win32 closes the error happens
2. Win32 App 2: In the other case we are aware of a Save Dialog is used and then the Win32 .exe is closed and see the error

Comments:
1. Microsoft Windows Automation Framework: UIAutomationCore.dll - The underlying code (sometimes called the UI Automation core) that handles communication between providers and clients. https://msdn.microsoft.com/en-us/library/ms747327(v=vs.110).aspx

2. This is only seen on a Windows 10 machine with a touchscreen or on Windows 10 without touchscreen monitors and the automation is enabled (not sure everything that might enable the automation) but Settings - Ease Of Access - Narrator will enable automation.

3. On Windows 10 machine without touchscreen monitors and no automation activated the error does not happen

4. The Win32 applications do not use the Automation Framework and therefore do not make any direct calls to it.

5. Process Explorer shows SysWOW64\UIAutomationCore.dll loaded for both Win32 applications mentioned with touchscreen monitor or automation enabled. It is not loaded for windows 10 machine without touchscreen and automation not enabled.

6. It appears to be happening between FormClose and FormDestroy - we are getting the Delphi IDE setup on a Windows 10 machine to see if we can find more info about the issue with the debugger.

Edited by: Brian Clingan on Feb 22, 2017 9:36 PM
Jony Bassan

Posts: 1
Registered: 2/20/09
Re: Delphi 2007 Win32 .exe closes with AV (Access Violation) in uiautomation.dl  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 12, 2017 3:26 AM   in response to: Brian Clingan in response to: Brian Clingan
Brian Clingan wrote:
Currently, we are seeing an AV in UIAutomationCore.dll when a Win32 .exe application closes. This is a software product that has been running on Windows XP, Windows 7 and now running it on Windows 10. Have only seen this issue on Windows 10.

Note: The Win32 applications are built using Delphi IDE 2007

Application Error: Exception EAccessViolation in module uiautomationcore.dll at 0006AOC9.

Cases:
1. Win32 App 1: In the first case every time the Win32 closes the error happens
2. Win32 App 2: In the other case we are aware of a Save Dialog is used and then the Win32 .exe is closed and see the error

Comments:
1. Microsoft Windows Automation Framework: UIAutomationCore.dll - The underlying code (sometimes called the UI Automation core) that handles communication between providers and clients. https://msdn.microsoft.com/en-us/library/ms747327(v=vs.110).aspx

2. This is only seen on a Windows 10 machine with a touchscreen or on Windows 10 without touchscreen monitors and the automation is enabled (not sure everything that might enable the automation) but Settings - Ease Of Access - Narrator will enable automation.

3. On Windows 10 machine without touchscreen monitors and no automation activated the error does not happen

4. The Win32 applications do not use the Automation Framework and therefore do not make any direct calls to it.

5. Process Explorer shows SysWOW64\UIAutomationCore.dll loaded for both Win32 applications mentioned with touchscreen monitor or automation enabled. It is not loaded for windows 10 machine without touchscreen and automation not enabled.

6. It appears to be happening between FormClose and FormDestroy - we are getting the Delphi IDE setup on a Windows 10 machine to see if we can find more info about the issue with the debugger.

Edited by: Brian Clingan on Feb 22, 2017 9:36 PM

I have the exact same problem with a project built with Delphi 2009. The product executes properly on XP, and win 7 , but has the UIAutomation error on Win10 with Touch screen.

Jony Bassan

Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02