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

Resolved User Unable To Open Multiple Windows in MDI

  1. Issue
0
Votes
Undo
  1. Joe Hess
    Joe Hess
  2. PowerBuilder
  3. Wednesday, 20 May 2020 16:35 PM UTC

Long shot, but I thought I would see if anyone has had this problem. I have a particular user that starts the work day with no problems. After a few hours of work, he is only able to open a single window at a time. All windows must be closed before he can open a new one. Restarting the application allows him to work for a few more hours before the issue happens again.

A few bits of information:

1) This is PowerBuilder version 9.0

2) He is the only user reporting this problem (doesn't mean others have not experienced it).

3) The application is using PowerTool Navigator

4) He generally works with the same 4 windows

 

I have looked at handle usage for the windows he repeatedly opens. Everything seems to be ok. I double checked that all objects created are being destroyed. I would probably guess this has something to do with PT Nav, but I thought I'd check for other ideas.

 

Regards,

Joe Hess

 

Creating xml templates for datawindow...
SelectionChanged problem with 2019r2
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 21 May 2020 18:48 PM UTC
  2. PowerBuilder
  3. # 1

Hi Joe;

   Would this be coincidental of the App users moving to W10 (which PB 9 was never certified for)?

Regards ... Chris

Comment
Joe Hess
  1. Joe Hess
  2. Thursday, 21 May 2020 19:01 PM UTC
This particular user is still on Windows 7. We are moving off-premise in a few months, so we did not bother updating the O/S on the local desktops.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 21 May 2020 19:38 PM UTC
Are you running the PB App(s) through RDP and/or Citrix?
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 20 May 2020 19:54 PM UTC
  2. PowerBuilder
  3. # 2

A lot of improvements made since PowerBuilder 9.  How about testing trial version of PowerBuilder 2019 R2 to see if it resolves your problem?

Comment
Joe Hess
  1. Joe Hess
  2. Thursday, 21 May 2020 19:04 PM UTC
I'm in the process of migrating to 2019 R2. The application is large and very old. There are too many things that do not work or behave differently. I cannot just recompile and set them loose.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 21 May 2020 19:31 PM UTC
I understand. Just wondering if you could do a quick test on to see if that particular problem still exists. I guess maybe hard to reproduce if only happens after few hours of really using the application.
  1. Helpful
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Wednesday, 20 May 2020 18:49 PM UTC
  2. PowerBuilder
  3. # 3

Hey Joe, You already checked my main concerns: GDI handles, memory consumption, etc.

I would like to see difference on these numbers between (A) when app opens and (B) AFTER app starts to act up weird. My bet is that SOMEWHERE something is picking up some resource that isn't released/unlocked.

Maybe released/unlocked most of the time - but SOMETIMES not - and then issues arise.
I remember in PB9 specifically there was a memory like in the XML parser which led to 10kB mem loss at every call. No issue - unless your app like mine SOMETIMES processes 1000s and 1000s of 1kB XML documents - and then sits back relaxing until next batch. Such behavior could lead to exactly the behavior you identified.

Good luck,
/Michael

Comment
Joe Hess
  1. Joe Hess
  2. Thursday, 21 May 2020 19:06 PM UTC
I will monitor the numbers to see what happens. I've also added some logging to track his activity. Maybe that will give me a clue.



Thanks
  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.