bug report - program up time

delphi package - automated exception handling

bug report - program up time

Postby Han312 » Fri May 10, 2019 9:42 am

You list in the bug report the "program up time".
Is it the time for the current process or is there a chance that by mistake a wrong time is listed (if the program was started several times)?

I ask since we get sometimes reports with a program up time which seems to be much too high.
Han312
 
Posts: 42
Joined: Mon Mar 14, 2016 3:49 pm

Re: bug report - program up time

Postby madshi » Fri May 10, 2019 11:00 am

It should be the time of the current process. How high are those unrealistic times?

You can look at madExcept.pas "GetProgramUpTime". That's the function which is providing the information. I don't really see how this could produce wrong information. Maybe you see a potential problem with that function code?
madshi
Site Admin
 
Posts: 10098
Joined: Sun Mar 21, 2004 5:25 pm

Re: bug report - program up time

Postby Han312 » Tue May 14, 2019 10:59 am

I mean something similar like this.
The main thread let me believe that the program just started. I would have expected several seconds but I get some hours.

Code: Select all
program up time            : 5 days 3 hours
...
main thread ($e14):
0040922e +01e TRW.exe      System                  @GetMem
009d242a +02a TRW.exe      Vcl.Controls            TWinControl.MainWndProc
00916543 +023 TRW.exe      System.Classes          StdWndProc
7ffa697a +1bd USER32.dll                           DispatchMessageW
00b5d0ae +12e TRW.exe      Vcl.Forms               TApplication.ProcessMessage
00b5d123 +013 TRW.exe      Vcl.Forms               TApplication.HandleMessage
00b5d571 +0e1 TRW.exe      Vcl.Forms               TApplication.Run
01690e00 +700 TRW.exe      Trw_Start      278 +218 ProgrammStart
01691185 +015 TRW.exe      TRW            797   +3 initialization
7ffa69e2 +00e KERNEL32.DLL                         BaseThreadInitThunk
7ffa6a93 +01b ntdll.dll                            RtlUserThreadStart


In this case the user had an
exception class : EOutOfMemory
exception message : Zu wenig Arbeitsspeicher.
which could have caused it.
I also got an screenshot which let me believe that the time is correct.
Han312
 
Posts: 42
Joined: Mon Mar 14, 2016 3:49 pm

Re: bug report - program up time

Postby madshi » Tue May 14, 2019 1:52 pm

Why would you think that the program just started? Every normal main thread callstack will look like that. "TApplication.Run" is what the program executes when it starts, and then it stays forever within a message loop within "TApplication.Run". So even if the program has run for 5 years, the callstack will still contain the same callstack. "TApplication.Run" only returns when the program exits. So from the looks of it, there's no real reason to doubt the up time of 5 days 3 hours.

EOutOfMemory occurs if the process is running out of memory, obviously. This can occur either if your program tries to allocate too much RAM. E.g. this could happen if you try to read a 4GB file into RAM. Or it could happen if there are memory leaks in your program. Try checking for memory leaks.
madshi
Site Admin
 
Posts: 10098
Joined: Sun Mar 21, 2004 5:25 pm


Return to madExcept

Who is online

Users browsing this forum: No registered users and 7 guests

cron