Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved PB2017, Search Library entries and Crash. To much Matches?

  1. Issue
0
Votes
Undo
  1. · Dainis
    · Dainis
  2. PowerBuilder
  3. Tuesday, 19 December 2017 13:25 PM UTC

Faulting application name: PB170.EXE, version: 17.0.0.1666, time stamp: 0x59524117
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
Exception code: 0xc0000005
Fault offset: 0x00001ed7
Faulting process id: 0x848
Faulting application start time: 0x01d378a6db03553b
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE
Faulting module path: C:\Windows\system32\MSVCR100.dll
Report Id: 29ef03ba-e49a-11e7-8a37-534e57000000

[Solved] Trace file cannot be opened
PB Run Error vs Compiled EXE
Accepted Answer
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 19 December 2017 14:55 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi, I can reproduce your issue when searching in PB Library painter using PB 2017, build 1666.

What I did: I search for "IF" across 1 PBL, then a few more, then even more - until PB crashes.

Same type of crash in approx same time when using System Tree for search instead of Library painter.

74330 matches in 20PBLs => OK​

 

Searching for less common text across much larger code base has no issues so I guess it is an internal data structure containing the identified matches that runs over.

 

Comment
There are no comments made yet.
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 19 December 2017 15:32 PM UTC
  2. PowerBuilder
  3. # 1

Same thing happens in 12.5 so it isn't a new issue.

You can try using PBSearch instead: http://www.topwizprogramming.com/pbsearch.html

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 19 December 2017 14:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi Danis;

   I have been using PB 2017 since before GA and have not had one crash like this - and I do a lot of searches everyday on some pretty complex code. I would recommend trying an Optimize on each PBL in your PB APP and then a full build. Then retry the search again after restarting the PB IDE.

  BTW: I would also suggest applying Maintenance Release #1 as well (build 1681) that came out at the end of September.

Regadrs ... Chris

 

Comment
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.