1. Aron Cox
  2. PowerBuilder
  3. Tuesday, 18 June 2024 13:14 PM UTC

PowerBuilder 2019 2728

I am trying to work out exactly which bit(s) of code are slow for a particular customer. I turned on tracing in code for a particular routine, and after a couple of weeks have lots of PBP files. However when I try to open any of them in the Profiling Trace View tool, PowerBuilder exits with no error message. I can open them in the two other Profiling tools, but I don't think that helps me work out which line(s) of code was slow.

Can anyone recommend another tool to view these files, or a way to stop PowerBuilder crashing when I try to view them?


If it's any help the Windows Event Log shows this on PowerBuilder crash:

Faulting application name: PB190.exe, version:, time stamp: 0x6100e4a4
Faulting module name: PBSHR.dll, version:, time stamp: 0x6100e41c
Exception code: 0xc0000005
Fault offset: 0x00148744
Faulting process ID: 0x2ef8
Faulting application start time: 0x01dac17c8a2ef6f7
Faulting application path: F:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime\PBSHR.dll
Report ID: 8e2566e5-eca4-492b-9c73-ed9ad2027123
Faulting package full name:

Aron Cox Accepted Answer Pending Moderation
  1. Tuesday, 18 June 2024 16:50 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,

Thanks for your reply.

Running the application from an executable using TraceOpen, TraceBegin etc

I am trying to use the Profiling Trace View from the PowerBuilder IDE to open the resulting .pbp file and see some timing info. I'm hoping to see what's taking a lot of time. I can open the trace file in two out of the three Trace viewers, but unfortunately not the one I want.

I tried it on another developer's PC, PowerBuilder also crashed to desktop for them too.

  1. Chris Pollach @Appeon
  2. Tuesday, 18 June 2024 17:09 PM UTC
Hi Aron;

FWIW: I found that in my STD framework that uses this feature automatically that the profile viewer utilities were VERY sensitive and apt to crash if the TraceEnd and TraceClose commands were not properly executed in that order at the end of your tracing sequence or just before you App EXE finally closes. HTH

Regards .. Chris

  1. Helpful
  1. Aron Cox
  2. Tuesday, 18 June 2024 17:14 PM UTC
Hmm, I will double check my code, thanks. If I remember correctly I put them in the window close event, so I hope they have done their job.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 18 June 2024 16:44 PM UTC
  2. PowerBuilder
  3. # 2

Hi Aron;

  Are you ...

  • Running the App from the IDE with Application Profiling execution turned on?
  • Using the App EXE command line to turn on Execution Tracing?
  • Using PowerScript commands (ie: TraceOpen, TraceBegin, etc) to create a specific execution trace?

   Once the App Execution Trace file is created are you trying to ...

  • Use the Profile Viewer utilities from the IDE to review the trace data?
  • Build a real-time trace viewer using the BuildModel PowerScript command?

Regards .. Chris

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.