Application crashes: Win 10 PB 12.6 build 3506 on SelectionChange event

[Former Member]

Hi everybody.

In a DropDownListBox (ddlb) on a SelectionChanged event, my application crashes RANDOMLY. I get from PB the message attached. BUT I can certify that functions work well in Windows XP and 7. So, I suppose it is sstill a problem of compatibility with Windows 10, as I got previously in Windows 8 and PB 10, but corrected in PB 12.6

Did you record a such dysfunction ? Crash occurs in a complete random way, whatever is the value chosen.

The logic is to choose a value in a first ddlb_1 (here COMMERCIALISER has been chosen) and then display in a second ddlb_2 the list of values below (here just one value 410_IMMOBILIER). At the end of the display PB crashes or not !! it dépends on its mood ! I noticed that it might depend of the quality of the click or the tactil touch ! But I am not sure at all !

Thank you for your diagnostic. Best regards. Didier (French from Paris)

[Former Member · Accepted solution]

Hi Dildier;

  Build 3506 was the 1st GA release of version 12.6. Unfortunately, that build was quite buggy in various areas and subject to stability issues as well. FWIW ... I would highly recommend moving up to the latest build (4091) and see if that clears your application issues.

Regards ... Chris

[Former Member · Accepted solution]

Hi Chris, Many thanks. I am going to (try to) unload the latest build 4091. Regards. I shall tell you, if I succeed ! I remember it had been so hard when I installed PB 12.6 with the SAP procedure !!

[Former Member · Accepted solution]

Hi Chris,

I updated my version 3506 by the latest 4091 (not difficult this time !) but the problem remains and the crash is always randomly. It occurs only with Windows 10 both in developement and runtime. I noticed using the version 4091 in runtime usage with just few PB dll that a new file libsybunic.dll is required when starting runtme application. Do you know its aim ? Are there others, but I recorded no more trouble, just the unsolved problem that is wasting my time ! Do you know how the problem can be studied to be solved one day ? I am still going to investigate by changing the code. May be I will find a substitution ?

Many thanks and Regards, Didier

[Former Member · Accepted solution]

Hi Didier;

  Sorry that the latest EBF did not cure your random crashing but at least your on (IMHO) a much more stable release.

  The libsybunic.dll library is normally used by the Sybase (now SAP) ASE database to support Unicode processing. I'm not sure this has to do with PB 12.6 - but, my guess would be for supporting the new ASE v16 client.

   It sounds like the random crashing is still probably related to your applications PowerScipt coding. I would have a look at various user events and even the if the "OTHER" event is coded. User events and the "other" can give stability problems if not coded properly.

   The other aspect is the use of external DLL's, 3rd party OCX's, etc around the applciation. We recently had a problem in a PB application that was calling the SnowBound (no Canada winter jokes here) imaging software. We eventually nailed the stability issue to those DLL's and in particular, a "finish" method that should have been called - that was not - that performed memory clean-up. When we moved to the newer MS-Windows, the memory management was not as clean as XP and thus the random crash. Calling the finish method corrected that issue but, what a PIA to find that one!

BTW: Does this application use the PFC framework?

Regards ... Chris

[Former Member]

Many thanks to all. I reorganized the various datawindow scripts (open and 16 ddlb) and now in Win 10 it works almost perfectly.at 99% while with win 7 it is always 100% OK. So the result is much better but I cannot prevent me from thinking that there is still a very very slight problem that I can explain by three possible causes. The quickness from  changing a  ddlb choice to another, the use of  the option showlist = TRUE and the position of the cursor (mouse or tactile) when clicking on a selected value. I send you an image of the datawindow wishing it can be visible. The aim is to display gradually multiple levels of a tree composed of activity costs, until 15 levels, so it is very dynamic with hide and reset functions..

Best regards, Didier

[Former Member]

Hi Dildier;

  FWIW:  I have also found that a lot of code in the open, clicked, constructor, activate, etc events can be an application killer as there are often a lot of related things going on at these times. Moving the bulk of my code to "posted" events and/or functions as normally made my code PB & O/S version proof.

   Posted methods fire when other related events and/or object state changes are completed. Also, I've found that event firing order or timing of these messages by the O/S can change across versions. Again, posting methods where your more intensive coding is processed guards against application crashing due to the above PB or O/S behaviour.

Just my $0.02.

HTH

Regards ... Chris

[Former Member]

This is just my guessing,

     1) Possible that ancestor object event is changed.. Try to regenerate descent objects that may help.

     2) If you are calling Triggerevent function, please check those events and make sure they all exists and match..

Regards,

Jahir.