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

Resolved Frozen after closing window

  1. Issue
0
Votes
Undo
  1. Richard Carrier
    Richard Carrier
  2. PowerBuilder
  3. Tuesday, 21 September 2021 14:36 PM UTC

I've got a datawindow that serves as a source data view/edit. Meaning it has over 200 columns and it needs them all before anyone ask.

The database is one table with 18k rows. This is tiny .

Data is retrieving longer than I expect and then when we close the window, do all the garbage collection recommended the system just freezes.

Got to task manager and you can see Appeon just slowly reducing its memory usage and then after about 30 seconds it finally unfreezes.

This is frustrating is your trying to use the tool.

We sometimes have 200k - 300k rows customers want to retrieve and then filter for analysis. So we had to set the StoragePageSize to Large and rows to disk is true.

I've never understood is you need both of those of does the PageSize do that for you thru virtual memory

 

Also, these machines are servers and have tons of memory and space and all ssd.

As always any help sincerely apprceiated.

Richard

Avoid/Stop scrollvertical in datawindow ?
PBAccessibility.dll causing application to crash.
Responses (6)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 21 September 2021 15:07 PM UTC
  2. PowerBuilder
  3. # 1

Hi Richard;

  In the DataWindow Control and/or DataStore's "Destructor" event, try adding the following ...

  • THIS.Reset()
  • THIS.DataObject =""

Note that "Rows to Disk" will have no effect if the DWO uses or contains either a Sort or Filter statement/command or computed fields.

HTH

Regards ... Chris

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 22 September 2021 21:18 PM UTC
Hi Richard;

The build I am using is 2728 for R3. This has been super stable and fast for me since its release on 2021.08.19.

If that is what you are using, then I would now suggest reinstalling.

Regards ... Chris

PS: I am using W10 version 21H1 build 19043.1237 on real PC's
  1. Helpful
Richard Carrier
  1. Richard Carrier
  2. Wednesday, 22 September 2021 21:32 PM UTC
Forgot to include we are running the PB IDE on a server 2016. Its been the same for 5-6 years or more . Only change has been updated maintenance.



Thanks
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 22 September 2021 23:14 PM UTC
Ahhhh ... The PB IDE is not certified or recommended for any Windows "Server" edition. Only the built App EXEs & runtime.

FYI: https://docs.appeon.com/pb2019r3/installation_guide_for_pb/ch01s01.html

Now saying that, your welcome to install the IDE on a Windows Server edition but Appeon does not support this.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Tuesday, 21 September 2021 19:45 PM UTC
  2. PowerBuilder
  3. # 2

this is a known issue - i've reported it.

 

https://www.appeon.com/standardsupport/track/view?id=3347

 

try adding to your DEPLOYED pb.ini file:

[Data Window]
ACCESSIBILITY=0

 

 

 

 

Comment
There are no comments made yet.
Richard Carrier
Richard Carrier Accepted Answer Pending Moderation
  1. Wednesday, 20 October 2021 20:20 PM UTC
  2. PowerBuilder
  3. # 3

I 100% don't agree and that's just an easy way out. My company has been using Powerbuilder since 2.0

 

This problem is also replicated on my local PC . Its not just a server thing. Its a DB driver or memory issue.

 

I've been developing using the server with massive amounts of data (300,000 rows) in previous versions of Appeon and everything worked great. It's one of these new releases this year.

 

In fact, it seem to start when Appeon created the new updated DB drivers for SQL

 

How can we get this at least looked at ?

 

Thanks

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 20 October 2021 20:46 PM UTC
Hi Richard;

You can try using the older SNC driver and see if that solves your stability issue with SS (I assume that you are using). A flakey DB driver can crash your App in the blink of an eye (and, possibly with no mini-dump in the O/S event log either).

Have you tried the IDE & App running on a real W10 machine? Your App EXEs though should run okay on Windows "server" editions. It's just the the IDE is not Windows "Server" certified (never was either under PowerSoft, Sybase or SAP either).

Please open a support ticket for this issue for Appeon to delve deeper into this problem. Just be willing to supply us with as much detail as possible along with a test SS DB & SQL (aka DWOs) in order to recreate the crash.

PS: have you tried an SQL trace?

Regards ... Chris
  1. Helpful
mike S
  1. mike S
  2. Thursday, 21 October 2021 17:52 PM UTC
have you tried 64 bit build of your application?
  1. Helpful
There are no comments made yet.
Richard Carrier
Richard Carrier Accepted Answer Pending Moderation
  1. Thursday, 21 October 2021 18:00 PM UTC
  2. PowerBuilder
  3. # 4

We attempted to convert to a 64 version but we use so many 3rd party DLL's for email, etc. that it would be a big nightmare.

 

 

 

Thank you for the suggestion.

Comment
mike S
  1. mike S
  2. Thursday, 21 October 2021 22:25 PM UTC
it would be interesting to see whether it would fix this particular problem though. if it does, then it might be worth your effort to replace the dlls, otherwise you are stuck with the way things are until appeon is able to fix this
  1. Helpful
There are no comments made yet.
Richard Carrier
Richard Carrier Accepted Answer Pending Moderation
  1. Thursday, 21 October 2021 22:34 PM UTC
  2. PowerBuilder
  3. # 5

Its not going to fix the problem, its a known bug in Appeon / the new database driver. has always worked perfectly up until this years releases. I don't know the exact release it started with. Thanks

Comment
Load more comments
mike S
  1. mike S
  2. Friday, 22 October 2021 14:47 PM UTC
did you try adding to your DEPLOYED pb.ini file:

[Data Window]

ACCESSIBILITY=0



because this fixed this exact problem for me.



Also, if you do a garbage collect on close of that window it will take time to do the garbage collect. Try turning that off if the pb.ini setting does not fix the problem. If that also has no effect, then turn off the rows to disk setting to see if that changes things.



  1. Helpful 1
Christopher Craft
  1. Christopher Craft
  2. Monday, 25 October 2021 17:37 PM UTC
We do deploy the PB.ini file with these settings but I will validate it is correct on the customers machine.

[Data Window]

NativePDF_IncludeCustomFont=1

Accessibility=0

[DataStore Behavior]

UseHwnd=no



I also do not have any garbage collect code or Rows To Disk setting.
  1. Helpful
mike S
  1. mike S
  2. Monday, 25 October 2021 18:26 PM UTC
build 2703



fwiw, i have 43K rows, 1242 pages. resizing the window is slow (recalc of page numbers most likely).

close of window = instantaneous. - driver used is oledb (the old one) with sql server.

close of window = instantaneous. - driver used is MSOLEDB (the new one)



dll version (build) = 2703

  1. Helpful
There are no comments made yet.
Zhang JX
Zhang JX Accepted Answer Pending Moderation
  1. Wednesday, 24 November 2021 01:52 AM UTC
  2. PowerBuilder
  3. # 6

Hi all, 

is there solution or alternative option for this?

We faced similar issue - frozen on windows closing, when retrieved with large set of data - which happened to Windows2016/2022 version only.

no such issue when deploying runtime application to Windows2018R2 server.

suspect problem with PB SQL driver.

Regards,

JX

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.