![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
My application is crashing and it looks like ASA is the problem The problem is when I close certain windows the app will crash and report that PBSHR110.dll reported the fault. Now to confirm that the DB is the problem I removed the retrieve and then on closing the window the app no longer crashed. So assuming it is a memory corruption problem I did the following: Validate the ASA 9 DB Did an unload and reload into ASA10 Defragmented the drive But this did not fix the problem of the app crashing.. How does one fix a DB if there is memory allocation problems?? Thanks |
#3
| |||
| |||
|
|
Hi Matt, from what you've experienced it is rather unlikely that ASA crashes the application. I'd recommend either debugging the app or using the /PBDEBUG switch to find the exact place in your code where it crashes. Also check wether you've only one version of PB runtime DLLs on the system. HTH Chris Werner f+s software gmbh "MattN" <mjnNOPam (AT) gmail (DOT) com> schrieb im Newsbeitrag news:4721c0df$1 (AT) forums-1-dub (DOT) .. My application is crashing and it looks like ASA is the problem The problem is when I close certain windows the app will crash and report that PBSHR110.dll reported the fault. Now to confirm that the DB is the problem I removed the retrieve and then on closing the window the app no longer crashed. So assuming it is a memory corruption problem I did the following: Validate the ASA 9 DB Did an unload and reload into ASA10 Defragmented the drive But this did not fix the problem of the app crashing.. How does one fix a DB if there is memory allocation problems?? Thanks |
#4
| |||
| |||
|
|
Yeah have already done that but could not work out how to go from there. I created a sample app not using pfc libraries and the crashing on close no longer happened. Also when removing the retrieve the close does not cause a crash so would assume it has something to do with the retrieve... So thought it might be the pfc files and replaced them but still the same problem. Also put the pbl's ona brand new machine with no other PB dll's but still the same result. Any other ideas? I did a PBdebug trace and found the last function to be called before the crashing occurs is as follows: Executing event +CLICKED for class M_EXIT, lib entry PFC_M_MASTER .............. Executing object function CLOSEUSEROJECT for class W_MAIN1, lib entry W_MAIN1 ..................... Executing object function +DESTROY for class TRIVERTEX, lib entry N_CST_XPLISTBAR_GRADIENT This is the last event before the crash. Chris Werner wrote: Hi Matt, from what you've experienced it is rather unlikely that ASA crashes the application. I'd recommend either debugging the app or using the /PBDEBUG switch to find the exact place in your code where it crashes. Also check wether you've only one version of PB runtime DLLs on the system. HTH Chris Werner f+s software gmbh "MattN" <mjnNOPam (AT) gmail (DOT) com> schrieb im Newsbeitrag news:4721c0df$1 (AT) forums-1-dub (DOT) .. My application is crashing and it looks like ASA is the problem The problem is when I close certain windows the app will crash and report that PBSHR110.dll reported the fault. Now to confirm that the DB is the problem I removed the retrieve and then on closing the window the app no longer crashed. So assuming it is a memory corruption problem I did the following: Validate the ASA 9 DB Did an unload and reload into ASA10 Defragmented the drive But this did not fix the problem of the app crashing.. How does one fix a DB if there is memory allocation problems?? Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |