Bug 6623

Issue with memory of power object array 09 June, 2021

Shilpa Rani Bansal
18 May, 2021
Product: PowerBuilder Category: PowerScript
Version: 2019 R3 Build:
Classification: Issue Publishing: Public
Priority: P1
Status: Closed Reason: DUPLICATE
Chris Pollach @Appeon 18 May, 2021
Hi Shilpa;

  Yes, that looks like the same issue as ...

  My guess is that the PBVM runtime is treating the structure like a REF pointer somehow and not like a local instance. I will talk with Ken later. He starts his shift around 8:30pm tonight.

Regards ... Chris
Shilpa Rani Bansal 18 May, 2021
Thats right, the value 9874544444 we are assigning  to a local structure and then we are copying this local structure into powerobject args.
Chris Pollach @Appeon 18 May, 2021
Ahhh - I think that I see it .. looks like all the 5 values in the sub array for the "Subscriber_no" field are set to "9874544444" (instead of the 5 individual values set in the Response Window.

Is that the issue that you are reporting?
Shilpa Rani Bansal 18 May, 2021
If you want we can have a call with my screen shared and I can show you the problem live over shared session.
Shilpa Rani Bansal 18 May, 2021
Thanks Chris, now i am able to view  issue#6606. And regrading reproducing the issue, we are using 2019 R3 MR#2703 on Windows sever 2016.
And the powerobject args are NOT OK. you have to run the code in DEBUG mode and see the values of those 5 args.
Chris Pollach @Appeon 18 May, 2021
Hi Shilpa;

  If you want more people in your organization to see ticket #6606, please let us know their email addresses and we can add them to Ticket#6606 OR Namdev can just change the privacy to "public".

  Note: I just tested your Test Case PB app that you attached to ticket #6606 this morning and the PowerObjectParm structure sent & received OK with 5 elements ARG units returned from the response window. So I cannot see any issues here. 

  BTW: I am using PB 2019R3 build 2703 on W10 20H2 build 19042.985 to test your case with.

Regards ... Chris
Shilpa Rani Bansal 18 May, 2021
Bug#6606 is private ticket so only the dev who opened it can track the status. Since it is critical issue multiple devs has to track the status of this ticket. Please re-open this ticket or make add me to view the status of 6606.
Chris Pollach @Appeon 18 May, 2021

*** This bug has been marked as a duplicate of bug 6606 ***
Chris Pollach @Appeon 18 May, 2021
Hi Shilpa;

  Since this the same problem as Ticket #6606, I will link them together and then close this ticket. Please continue to communicate through ticket #6606 and only open a new one for a new issue.

Thank you for understanding.

Regards ... Chris
Shilpa Rani Bansal 18 May, 2021
Tracking status of Private ticket (https://www.appeon.com/standardsupport/track/view?id=6606)
The code for reproducing the issue is already provided.

Remarks: Please note, this is a highly critical issue as we have Production with PB 2019 R3 in 2 weeks. Please assign a POC on priority and update the status of ticket here also along with in private ticket.
Windows Server 2016
Database Type:
Database Version: