1. Pierre DETE
  2. PowerBuilder
  3. Monday, 14 October 2019 15:06 PM UTC

Hi All, 

One of our customers has a problem opening a window on his Amazon AWS Appstream system runing our Powerbuilder appication.
At the moment, only one window is involved. It's a standard window (99864 Bytes) nothing special in it.
Powerbuilder falls into"Not Responding" and consumes 50% of the cpu without ending.
The application works well outside the Appstream environment.
For the moment we have tried unsuccessfully to update Windows redistributable c++ to (2015-2019) and we have increased the heapsize to 1024/20408/2048.
What can we look at?
Thank you in advance for your help.

Pierre

 

Pierre DETE Accepted Answer Pending Moderation
  1. Friday, 8 November 2019 16:27 PM UTC
  2. PowerBuilder
  3. # 1

Hi All,

 

Finaly there was a bug in our code enterin in an infinit loop will decoding printer devices list string as with Appstream there was some ';' missing.

Sorry.

Comment
  1. Michael Kramer
  2. Friday, 8 November 2019 17:12 PM UTC
Most important is that you found the root cause and know how to fix it. Good luck.
  1. Helpful
There are no comments made yet.
Pierre DETE Accepted Answer Pending Moderation
  1. Tuesday, 15 October 2019 08:54 AM UTC
  2. PowerBuilder
  3. # 2

Hi, thank you for the reply, the customer says :  now there only Appstream 2.0 available on Amazon ...

 

Regards

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 15 October 2019 19:01 PM UTC
Anything useful in the "Appstream" logs?
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 14 October 2019 16:00 PM UTC
  2. PowerBuilder
  3. # 3

Hi Pierre;

  I wonder if it's an issue of the AppStream 2.0 client software  that gets downloaded where the version and/or configuration is different on this one user's PC?

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