Strange exception on app shutdown

jbeyer

One of our customers has sent us a somewhat strange exception that seems to be eminating from the TCustomElGraphicButton class when our application is shutdown.  I can't reproduce it myself.   Does anyone have any idea what could cause this? or even where to begin looking for a fix?

Thanks!

John

 

MadExcept output (some identifying information removed):

----------------

date/time         : 2013-03-04, 10:48:11, 28ms
computer name     :
user name         :
registered owner  :
operating system  : Windows 7 x64 Service Pack 1 build 7601
system language   : German
system up time    : 3 hours 23 minutes
program up time   : 1 hour 16 minutes
processors        : 8x Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
physical memory   : 3045/8149 MB (free/total)
free disk space   : (C:) 38,34 GB
display mode      : 1280x1024, 32 bit
process id        : $17b0
allocated memory  : 454,58 MB
executable        : MYAPP.exe
exec. date/time   : 2013-02-14 11:57
version           : 4.0.0.312
compiled with     : Delphi 2009
madExcept version : 3.0l
contact name      :
contact email     :
callstack crc     : $4529e001, $c80d1437, $e46d1bd5
exception number  : 5
exception class   : EIntOverflow
exception message : Integer overflow.

main thread ($1f9c):
4529e001 +000 ???
501c565a +2d2 vcl120.bpl   Controls          TControl.WndProc
773bec5f +063 ntdll.dll                      bsearch
501ce117 +083 vcl120.bpl   Controls          TWinControl.WMPrintClient
501c565a +2d2 vcl120.bpl   Controls          TControl.WndProc
501c9ce7 +513 vcl120.bpl   Controls          TWinControl.WndProc
501c9400 +02c vcl120.bpl   Controls          TWinControl.MainWndProc
773a0107 +02b ntdll.dll                      KiUserCallbackDispatcher
501c565a +2d2 vcl120.bpl   Controls          TControl.WndProc
0062f578 +23c MYAPP.exe    ElPopBtn 5261 +53 TCustomElGraphicButton.WndProc
501c565a +2d2 vcl120.bpl   Controls          TControl.WndProc
501c9ce7 +513 vcl120.bpl   Controls          TWinControl.WndProc
773a0107 +02b ntdll.dll                      KiUserCallbackDispatcher
50058e67 +02b rtl120.bpl   Classes           TDataModule.DoDestroy
50058d3b +027 rtl120.bpl   Classes           TDataModule.BeforeDestruction
50007259 +009 rtl120.bpl   System            @BeforeDestruction
50058d46 +006 rtl120.bpl   Classes           TDataModule.Destroy
50057a1b +047 rtl120.bpl   Classes           TComponent.DestroyComponents
5000865d +065 rtl120.bpl   System            @Halt0
011eb39c +118 MYAPP.exe    MYAPP   283 +54   initialization
760333a8 +010 kernel32.dll                   BaseThreadInitThunk

Victor_Bocharov

Hi,

What theme settings are used on client machine and (if any) for the application itself? 

jbeyer

I'm not sure about what theme is used for the Client OS.  For the elPack components, we typically set the properties (at designtime) to:

ThemeGlobalMode := False;

ThemeMode := ttmPlatform;

But I can't guarantee that 100% of the elPack components across all 150 or so of our forms are set that way tho.  We don't use any of the style properties.

I had a feeling it had something to do with the theming...only thing I could find googling on TWinControl.WMPrintClient was something about theming problems in D2007.

This is a D2009 compiled app...so it doesn't use the Delphi native theming of newer versions.

Rafael Maricca (LMD)

Only just to be sure: You are using a recent ElPack version (current version is 2013, release 11.x)? 

I remember such a problem, but this was a couple of years ago.