Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved PowerBuilder-application crash (COMCTL32.dll)

  1. Issue
0
Votes
Undo
  1. Michael Volkert
    Michael Volkert
  2. PowerBuilder
  3. Friday, 17 December 2021 10:44 AM UTC

Hello,

we have a problem with random crashes reported by the users of our native PowerBuilder-application.
The application just shuts down on different actions in the application, so we don't know what exactly causes it.
The only hint we could find is a Windows Error-Event regarding the COMCTL32.dll:

Faulting module name: COMCTL32.dll, version: 6.10.18362.1916
Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.1916_none_e6276c4ef8de06c3\COMCTL32.dll

Our users run on 64-bit Windows 10.
We use PowerBuilder Version 2019 R2 Build 2353.
For building the application we are using the integrated PowerBuilder-Compiler.

We would be glad for any help.

Thanks.

datetime format in powerscript
Datawindow input / checks and so on with paste op...
Responses (5)
Roland Mühlberger
Roland Mühlberger Accepted Answer Pending Moderation
  1. Tuesday, 20 December 2022 13:51 PM UTC
  2. PowerBuilder
  3. # 1

Sorry to comment an old discussion, but did anybody ever solve the comctl32.dll problem? We also have random crashes in comctl32.dll.

We use pcode and the 32 bit versions of the runtime. We do not deploy the comctl32.dll, the one from the OS is used.

It does not seem to be an issue with a specific version of comctl32.dll, we see crashes with different versions at different customers sites.

Regards,

Roland

 

Comment
There are no comments made yet.
Michael Volkert
Michael Volkert Accepted Answer Pending Moderation
  1. Monday, 20 December 2021 13:00 PM UTC
  2. PowerBuilder
  3. # 2

Hi John,

1. It's being deployed as exe/dlls.

2. 32-bit. We could try building a 64-bit Version and see if that helps.

3. We are not using any frameworks

4. No, it's not bundled with the app. It seems it's taking it from Windows, based on the faulting module path ("C:\Windows\WinSxS\...").
The application is using 6.10, which seems to be the latest based on your link.

We'll start a try with the 64-bit. Thank you.

Regards Michael

Comment
John Fauss
  1. John Fauss
  2. Monday, 20 December 2021 14:35 PM UTC
As an experiment, try deploying as p-code (.pbd's). Are you also deploying all of the PB runtime DLL's, or are you trying to deploy only a minimal subset? If you're not including all of the runtime DLL's, I suggest you try that, too.



Is this the first deployment from a previous PB version? Make sure you are not trying to run the app with a mixture of runtime DLL's from different PB versions.



If I were in your situation, I would also throw together a very small, single-window ttest application. Build/deploy it as exe/dll and see if that works. If it works, then there is likely something unique to your application causing the problem. Do you get any warnings when compiling the app?
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 20 December 2021 16:27 PM UTC
Hi Michael, I don’t suggest you try 64-bit… it’s going to create more problems and I doubt that is the reason.
  1. Helpful 1
There are no comments made yet.
Michael Volkert
Michael Volkert Accepted Answer Pending Moderation
  1. Monday, 20 December 2021 12:41 PM UTC
  2. PowerBuilder
  3. # 3

Hi Chris!

the problem is that we don't know where the comctl32.dll is being called. We are not using it directly. The application crashes on many different actions. 

Regards Michael

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 20 December 2021 17:25 PM UTC
Check and see if it;s being used n an external function call. For example ...

FUNCTION Boolean InitCommonControlsEx ( ulong pInitCtrls [ ] ) library "comctl32.dll" alias for "InitCommonControlsEx"

  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 17 December 2021 15:02 PM UTC
  2. PowerBuilder
  3. # 4

Hi Michael;

  Since this is a random crash ... I would suggest adding a TRY..CATCH PowerScript block around the "COMCTL32" logic. Often to the catch operation, the "Exception" object's information from the CATCH can direct you to the actual issue causing the problem. The TRY..CATCH should also allow your App to recover under program control and continue without crashing. Food for thought.

Regards ... Chris

Comment
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Friday, 17 December 2021 14:37 PM UTC
  2. PowerBuilder
  3. # 5

Greeting, Michael -

Some additional information, please:

1. Is the PB app being deployed as exe/pbd's (p-code) or exe/dll's (machine code)?

2. Compiled as 32-bit app or 64-bit?

3. Is the application built upon a framework, such as the PFC? If so, which framework and what version? Is there a newer version available?

4. Are you deploying comctl32.dll with the PB app? If so, where did this version come from?

A resource I have checked with (URL below) shows that comctl32.dll version 6.1 was distributed with Windows Vista, Windows Server 2008 and Windows 7. Maybe try using the one included in Windows 10?

https://docs.microsoft.com/en-us/windows/win32/controls/common-control-versions

John

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.