php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #6571 memory leak when selecting text type fields
Submitted: 2000-09-06 03:23 UTC Modified: 2002-01-27 05:20 UTC
From: philip dot day at edt dot ericsson dot se Assigned:
Status: No Feedback Package: Sybase-ct (ctlib) related
PHP Version: 4.0.2 OS: solaris 2.7
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: philip dot day at edt dot ericsson dot se
New email:
PHP Version: OS:

 

 [2000-09-06 03:23 UTC] philip dot day at edt dot ericsson dot se 
I am using the latest 11.1.1 openclient ct-lib.  The database server is 11.9.3.  I can connect, update and select without problems but as soon as there is a text type field in the result then the httpd process serving the request (apache 1.3.12) grows by 60 mb (topping out at 135 mb). I get the same problem with ct-lib running php 3.0.12 as well.  I can use db-lib with 3.0.12 (same script), which works fine, so it's not a problem but php 4.0.2 doesn't work at all with db-lib..

regards Philip


/configure  --with-apxs=/opt/local/apache-ssl/bin/apxs  --prefix=/usr/local --with-ldap=/usr/local/ldap --with-mcrypt=/usr/local/ --with-config-file-path=/opt/
local/apache-ssl/conf --enable-debug=no --enable-magic-quotes --enable-bcmath --enable-track-vars --with-sybase-ct=/opt/sybase/openclient/11.1.1 --without-mysql

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-09-07 03:48 UTC] philip dot day at edt dot ericsson dot se 
I think I've found the cause: The call to ct_describe made in sybase_result returns the max length of a text or image field (a very large value) in the maxlength property, rather than the actual length that is required for tmp_buffer.  I tried changing maxlength property to a fixed value and the memory leak vanished.  I'll try to figure out how to get the actual value.
 [2002-01-06 09:05 UTC] mfischer@php.net 
Is this still valid for 4.1.1 ?
 [2002-01-27 05:20 UTC] sander@php.net 
No feedback.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Mon Oct 07 12:01:27 2024 UTC