Hi Ken:
I'm sorry I am not replying directly to you, it wouldn't allow me to add a screenshot there.

First, we cannot consistently reproduce it, and even if we could our application is huge and based on a multi GB database. BUT, I have noticed something with this particular crash, right before the system crashes, it spawns up another application with no username, and memory associated with it (see the one outlined in red in the screenshot).  What would cause this to happen?  It might be the clue to finding a solution.

MJ

One trick we use to improve image quality is to set their transparency=1.    Images like this are rendered slightly differently as they need to blend with their background and end up with edge smoothing and seem to look a lot better.   Unfortunately you cannot do this with images rendered via computed fields using the bitmap() function or images on buttons.

Mark

Hi all:

Quick update.  We've been beta testing a version without out 3rd party image tool and, as far as functionality goes, it is ok, but we aren't sure yet whether or not it is better with the 3rd party image tool or just PB.  There is still a memory leak, and while we are still experiencing crashing, we've confirmed it isn't because of the GDI Object count (which research indicated that was a contributing factor to the prior version).  With both versions we experiencing crashing in about the same amount of time.  Because the PB_HEAP_LOGFILE isn't an option (resolving that issue has been moved to 'enhancements'), I've gone to the Event Viewer and the message is consistently the same. 

I will post it here in case anyone has any suggestions - or, if you feel it better I create a separate post, I will do so:

Faulting application name: a_replace.exe, version: 1.0.0.1, time stamp: 0x625eda81
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22
Exception code: 0xc000041d
Fault offset: 0x000000000002cd29
Faulting process id: 0x3500
Faulting application start time: 0x01d934d7cbf4855c
Faulting application path: [our builds path]

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: fac85f41-0bc7-45fb-b0ff-780702f0cd89
Faulting package full name:
Faulting package-relative application ID:

If anyone has any suggestions or has experienced the same issue, I'd love to hear them!

Thank you.

MJ

Hi All and thank you for the great suggestions.

Here are the things we have tried, and the results:

• Image Gallery (ranked in worst to best option so far)
  • Picture List Box - can only show one image per line
  • ListView Object
    • Too slow to render more than 500 images
    • Images are fuzzy
  • Web Control
    • Display is inconsistent; sometimes it does not display all the images and requires a refresh
    • Image quality is good
    • Speed is slower - both the speed to draw initial page and the speed to draw our larger galleries
  • Dynamically create gallery using custom user object 
    • Image quality good
    • Speed is slower when greater than 800 images
  • N-Up datawindow - Display as Picture
    • Speed is good, even on >7K images!
    • Images are poor quality.  Thumbnails are fuzzy and not crisp
      
      • Tried using larger images
      • Tried using smaller, more optimized images for the gallery size
      • Tried making size displayed bigger - helped marginally, but still fuzzy
      • We believe this is how PB converts the image when using this feature and it looks like we have no control over this, as it is just a checkbox.  Is there anyone out there who knows a way around this?  We believe it is converting the images to a 256 .bmp.

Happy Monday!

MJ

Hi Mary,

I suspect the issue may have something to do with PB 2019 R3 starting to support UI Automation. So I suggest you try this:

1. Open the PB IDE pb.ini file (C:\Users\%username%\AppData\Local\Appeon\PowerBuilder 21.0\pb.ini). Add ACCESSIBILITY=0 under the Data Window node and then try again:
[Data Window]
ACCESSIBILITY=0

2. If you compile your application to an EXE to run, then you need to add a pb.ini file to the directory where your PBapp.exe resides, and this file contains the following content.
[Data Window]
ACCESSIBILITY=0

If the issue remains, I suggest you submit a bug to the Appeon Support System(https://www.appeon.com/standardsupport/newbug) and upload a small reproducible case there for our analysis.

Regards,
Ken

Hi MJ;

  Sounds like maybe a 64bit OLE issue (as a guess). Is the PB 2017 Rx based version of the App 64bit as well?

Regards ... Chris