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

Resolved PowerBuilder Crash due to User Object limit

  1. Issue
0
Votes
Undo
  1. Devang Modi
    Devang Modi
  2. PowerBuilder
  3. Wednesday, 28 November 2018 12:07 PM UTC

Hello Experts,

 

We are facing issue while opening multiple windows. As part of Opening multiple windows. System creates Datawindow objects. We noticed that when User Object reached 240 / 250 limit then system is started to crash. 

 

Do we have any limitation in system on User Object? 

 

Thanks & Regards,

Devang Modi.

  1. Crash
  2. Memory Leak
  3. PowerBuilder (Appeon)
  4. User Object
Application is getting crash after migration to PB...
PB source control connections - a blowup, and none...
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 28 November 2018 15:43 PM UTC
  2. PowerBuilder
  3. # 1

Hi Devang;

   If your App uses Data-stores - try this ...

  1. Create a PB.INI file & save this in your App's EXE folder
  2. Add the following to your PB.INI

[DataStore Behavior]
; No = do NOT use MS-Window handles in DS processing (Default is yes). "No" gives much better performance and l;ower memory overhead!
UseHwnd=no

If that works for your App's EXE, try editing your PB IDE's PB.INI adding the same settings.

Regards ... Chris

 

Comment
Roland Smith
  1. Roland Smith
  2. Thursday, 29 November 2018 02:51 AM UTC
It would be nice if the help listed all these secret pb.ini runtime settings. The only written documentation are in forum posts.

I think the whole idea of requiring a pb.ini file to be installed with the exe is stupid. Instead there should be a function that we can use. I would be in favor of a generic function called RuntimeSetting or similar.
  1. Helpful
Devang Modi
  1. Devang Modi
  2. Thursday, 29 November 2018 05:34 AM UTC
Thanks a lot Chris. I will try and update about it.



Thanks a lot for your quick reply. Really appreciated it. Do we have documentation of all such values in PB.INI ? It will help a lot.



Due to such issues of PB, customers are getting fed up with Applications. We need to be innovative and document such issues for big applications.



Thanks & Regards,

Devang Modi.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 29 November 2018 14:49 PM UTC
Hi Devang;

By chance, is this a PFC based application?

Regards ... Chris
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 28 November 2018 15:32 PM UTC
  2. PowerBuilder
  3. # 2

Maybe you should ask yourself why you have 250 or more DataWindow objects available at one time. It sounds like a poor user interface design to me.

 

Comment
Devang Modi
  1. Devang Modi
  2. Thursday, 29 November 2018 06:58 AM UTC
Hi Ronald,



We have application, where customer can open multiple account screen (screen for different customers). So for each Screen, we are presenting so much information about Customer. In this screen we have around 10-12 Datawindows & datastores as well. We can't restrict users that they should not open these number of screens in production.



Thanks & Regards,

Devang Modi.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Thursday, 29 November 2018 14:33 PM UTC
The pb.ini change should reduce the memory requirements of your datastores but may prevent them from being printed, Chris would have to chime in on that.

Make sure the datastore objects are created only when needed and destroyed as soon as they are no longer needed. Never create a datastore within a loop. Also, you can create one datastore object and assign different datawindow objects to it as needed instead of creating multiples.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Thursday, 29 November 2018 14:35 PM UTC
Tab objects have an option to only be created when the user clicks on it. Using that will reduce memory use as it is likely some tabs are rarely used.
  1. Helpful
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.