Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Why does my search crash PowerBuilder

Status
Not open for further replies.

Statey603

Programmer
Nov 10, 2009
196
US
I am fairly new to PowerBuilder. I am using 11.0 build 6525.

Whenever I search for a specific function (wf_get_dw_obj), PowerBuilder crashes (almost immediately). If I try searching for something else, like X1, it searches fine.

What would cause this to happen?


 
thought it surprises me: maybe one of your objects isn't compiled well.
Do a 'full rebuild' with right mouse button' on top of a target or on top of your workspace entirely.
Then do an 'optimize' of all of your pbl files (right mouse button also).

On the other hand, check on if you can download any more recent EBF (fixes).

Have you seen it might be related with finding a lot or little occurences of what you're searching for (thinking of memory problems)?




regards,
Miguel L.
 
OK.......I am seeing Search Crashes again and have more information.

The crash occurs only while searching for specific text in a specific PBL.

For example, when I seach for 'service authorization' in Test.pbl. Test.pbl is a collection of newly checked in development work. A co-worker indicated that sometimes the PBLs become unstable suspecting it has to do with the size of the PBL. We Optimized the PBL, but the Search still causes a crash.

I was wondering if anyone else has seen this type of behavior and/or knows how to fix it.

thanks.....
 
try to create one o more new libraries and copy the object from test.pbl to those new ones. do your search on those?

I've seen crashes like this (too many objects in one library) in the early days only .... (powerbuilder 2, 3, 4).

Are all of the objects 'checked-in'?

It might be a new bug with pb 11.

Do you have cyclic references: (a function that calls to itself, a window that referes to another is also referenced itself by the other one, etc.)?

If you're in a hurry anyway.... to find your references: export all the objects and do a "search in directory" using for example notepad++.

regards,
Miguel L.
 
I will try to check out those suggestions.
thanks....
 
Here is some additional information that I found.

I narrowed the Search Crash down to a specific PB window object: w_sh_srvc_auth.

Whenever I search for the text 'service authorization' it causes PowerBuilder to crash with an exception.

I am trying to zero in on the cause of the crash.

If I search for text 'service' it does not crash and returns 1185 references. I am guessing that the number of results returned by the search is not the issue since a search for 'service' will return more results than a search for 'service authorization'.

I appreciate any hints on how to check for possible corruptuion or other causes of this crash.
 
Very weird!

try to do an "optimize" of the pbl file that contains the object.
try to export the file to *.srw and after try to import it into a library???

regards,
Miguel L.
 
I already tried the Optimize a few times and it did not fix the problem.

I performed an export as suggested and opened the swr file with a text editor and performed my search and it only came back with 6 instances of 'service authorization' which is the search that always causes the crash. All of these instances are text strings in messagebox calls.

I was not sure about importing the SWR back into my PBL to see if that fixes it. Will it overwrite the existing object (w_sh_srvc_auth) that already exists in my PBL or will it take the name of the export (my_w_sh_srvc_auth.srw)? The last thing I want to do is cause further corruption. Please advise.

I still can't figure out why this search would cause PowerBuilder to crash [every time]. Could it be a PowerBuilder bug?


thnx
 
yes it'll overwrite your existing object (unless you change the information/name of the object in the first 2 lines of the exported code). For that reason you should create a new library (pbl) and import it into that directory. (it'll only give you a compiler warning about the other one allready existing).

yes it could be /probably is a powerbuilder bug, but can't be sure untill you try the import. It might just give some light on what's wrong.

I'd like to know if you zero down the problem.
good luck

regards,
Miguel L.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top