Bug in 3.1Refresh with SalArraySetUpperBound

[J.Bertram]

 Posted by:  Joerg P. Bertram 

Hello,

we have a big memory allocation problem with GTD 3.1 PTF3 Refresh, the same
works fine with CTD 2.1 PTF4. The function SalArraySetUpperBound ( UdvArray,
1, -1) did not work correctly. In some cases the virtual memory will not
released anymore it grows and grows...
I have made a little sample to show you the facts.

Best regards

Joerg P. Bertram
Dipl.-Informatiker
QM Competence Center

IDOS Software AG
Gerwigstr. 53
76131 Karlsruhe, GERMANY
Fon: +49 (0)721 962250
Fax: +49 (0)721 9622550

http://www.idos.de

[Dave Rabelink]

 Posted by:  Dave Rabelink 

Joerg,

I tested this in 3.1 PTF3 (no refresh version) and there the problem is also
present !!

This is a severe problem and must be resolved !

Did you report this (incl the sample) with LOG-A-BUG on the Gupta website ?
If not, please do so and report back the defect number in this thread.

[Jim McNamara]

 Posted by:  Jim McNamara 

Has anyone tested for this in TD2005?

[arvindram11]

 Posted by:  Aravind Ram 

Seemed to work fine in TD 2005 (i.e. I could not see any abnormal behavior
in the memory usage when the test was running).

Aravind

[J.Bertram]

 Posted by:  Joerg P. Bertram 

I have set it into the LOG-A-BUG. I am waiting for a reference number so
far.

[J.Bertram]

 Posted by:  Joerg P. Bertram 

This was the answere from Gupta:
----------------------------------------------------------------------------------------------
Log-A-Bug has reviewed the issue listed below and determined that this was
an existing defect.
Thanks you for the test case, with it I was able to reproduce the memory
leak issue and could see big chunk of lost memory, this happen indeed with
last TD310 PTF3. However testing that same application with T2005, I'm no
longer able to reproduce the leak issue. There have been many leak issue
fixed on TD2005, please have a look at the fix list on our side, you can
also download a trial version of TD2005.

Thank you,
Log-A-Bug
A Service of Gupta Technologies
Please visit us at our web site: www.guptaworldwide.com
For a list of fixes please visit us at:
http://www.guptaworldwide.com/Support/Default.aspx
Please visit our Log-A-Bug service in the future at:
http://www.guptaworldwide.com/Support/LogABug.aspx
To contact sales regarding services or support, please visit
http://www.guptaworldwide.com/Company/Contact.aspx for a
location near you.

Please do not reply to this email. It arrives in an automated inbox and
will not receive a response.
-------------------------------------------------------------------------------------------------
My answere:
It is nice to hear but we have applications in productions at our clients
who got the problem and we got big problems by this defect.
What will that answere mean? Will there no more PTF for TD3.1 that solve
this big problem?

Here the support table from
http://www.guptaworldwide.com/Products/Product_life_cycle.aspx

Team Developer
PRODUCT/ VERSION
STATUS
ENGINEERING SUPPORT RETIRED
TECHNICAL SUPPORT RETIRED

Team Developer 2005
In Engineering Support
dates will follow later

Team Developer 3.1
In Engineering Support
March 2006
2007

Team Developer 3.0
In Technical Support
January 2005
March 2006

Team Developer 2.1
Retired
Retired
Retired

Team Developer 2000
Retired
Retired
Retired

Team Developer 1.5.x
Retired
Retired
Retired

Team Developer 1.1.x
Retired
Retired
Retired

SQLWindows 5.0.5
Retired
Retired
Retired

We payed many money for GLS and TD 3.1 is always in the table. So it is a
must-be for Gupta to solve this problem, I think!

Best Regards

Joerg Bertram
IDOS Softwaresysteme GmbH

[Dave Rabelink]

 Posted by:  Dave Rabelink 

What does "existing defect" mean ?

IMHO there are no defects which are NOT existing.

If this answer means we 3.1 customers need to upgrade to TD2005
because they are not willing to fix 'existing' defects....

But this probably isn't the case.

We just ported to 3.1 from 1.5.1 after many years. And we are not
planning to port again to TD2005 in the near future. Also TD2005 will
have 'existing' defects which probably will be solved in TD2007 or
whatever version...

I expect that PTF4 will have this severe issue fixed, knowing that
they have fixed it TD2005 already.

But i ask Gupta to respond to this thread indicating that my
assumption is right that TD3.1 customers will be fully serviced as
expected !

[J.Bertram]

 Posted by:  Joerg P. Bertram 

Log-A-Bug has reviewed the issue listed below and determined that this is a
defect. The defect number is 83398. For further information watch for the
fix in the Fixes.Wri file in future PTF's or Releases.

Thank you,

Log-A-Bug
A Service of Gupta Technologies
Please visit us at our web site: www.guptaworldwide.com
For a list of fixes please visit us at:
http://www.guptaworldwide.com/Support/Default.aspx
Please visit our Log-A-Bug service in the future at:
http://www.guptaworldwide.com/Support/LogABug.aspx
To contact sales regarding services or support, please visit
http://www.guptaworldwide.com/Company/Contact.aspx for a location near you.

Please do not reply to this email. It arrives in an automated inbox and
will not receive a response.
________________________
Product: Team Developer
O/S: Windows XP
Version: 3.1
PTF: 3

There is a memory leak in the SalArraySetUpperBound function depending how
you use it (see example).

Joerg P. Bertram [Joerg.Bertram@idos.de]

[Dave Rabelink]

 Posted by:  Dave Rabelink 

Nice to see the defect will be solved.

[J.Bertram]

 Posted by:  Joerg P. Bertram 

I am very sad to see that bugfix 83398 is not in the list!

PTF4:
72856 Getting "Error code at invocation of FunctionName: 80020009" when
passing a variant to a COM Interface function of a CTD 2.0.00 COM Object on
a SetObject() call.
79870 Report builder Automation: Scroll Toolbar not showing. Scroll Toolbar
is grayed out.
80321 Some fonts are not getting set correctly on the buttons, group boxes,
background texts, check boxes and radiobuttons.
81384 When VisMenuInsertPicture is called, it is inserting with a different
font than the default.
81389 OLEDB consumer against INFORMIX client Connect 2.70 with OLEDB
provider v2.50.0: SqlPrepareSP() failing with blank error (error 0) when
using bind variable in parameter strStoredProc. If not using bind variable
SqlPrepareSP() does not fail.
81612 Unable to open a Report Builder report if its name contains 4 or more
double-byte characters in it.
81740 Very sporadically getting runtime error "cannot read file", followed
by "cannot read application file" when a 'main' application is loading a
Team Developer application using SalLoadApp().
82048 cOutlineListBox has painting problems after calling function
LoadOutline().
82075 SQL Server OLEDB provider: Using bind variable within ROUND()
aggregate function causes "Error '-2147467259 Syntax error or access
violation'".
82156 When there are two tables within a form class, wrong table column is
set if a function from another table window is called within a table.
82161 cQuickHTTP does not return correct Source or SourceSize depending on
certain URL values.
82206 Trying to use different trays on some printers doesn't work. Report
always prints from the top tray or tray 1.
82210 Menu shortcuts do not work in some circumstances, possibly related to
large number of menu items.
82211 SQLWindows executing wrong code in named menus in certain
circumstances, possibly related to large number of menu items.
82253 If first column of a source table window is set to Visible='No',
SalTblCopyRows() followed by SalTblPasteRows() will set first column of
target table window to NULL.
82513 When associating an image with a menu item via VisMenuSetPicture, the
menu item doesn't appear disabled visually. However, the message actions
aren't processed, indicating the item actually is disabled.
82529 When one uses a bitmap and an accelerator, the alignment of the hot
key is off when compared to menus that do not contain a bitmap.
82855 SQLWindows application crashes during compile after modifying and
refreshing a library file.
83507 An application saved in .APT format fails to load, locking/crashing
the SQLWindows IDE, in specific conditions.

So I hope PTF5 will come as soon as possible including this very strange
bug!