|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #20 Memory Leak
Submitted: 1998-01-28 18:41 UTC Modified: 1998-02-01 16:59 UTC
From: chris at enginered dot com Assigned:
Status: Closed Package: Oracle related
PHP Version: 3.0b3 OS: Solaris 2.5.1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
34 + 50 = ?
Subscribe to this entry?

 [1998-01-28 18:41 UTC] chris at enginered dot com
PHP3.0b3 as Apache Module with Oracle Support on Solaris 2.5.1

looks like a pretty nasty memory leak (oracle.c:743, oracle.c:787).

happens when getting TABLE_NAME from ALL_TABLES

(oh, also DESCRIBE causes a parser error).


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [1998-02-01 16:59 UTC] ssb
DESCRIBE is a command specific for the sqlplus program.
In other programs you have to look in the Oracle data
dictionary to find information about tables.

Try this for a start:
  SELECT * FROM user_tab_columns WHERE table_name = 'YOUR_TABLE'

The memory leak is fixed in revision 1.45 of functions/oracle.c
and will appear in 3.0b4.

 [2020-01-17 15:12 UTC]
Automatic comment from SVN on behalf of nikic
Log: Fix: Remove $serverctrls parameter from ldap_bind()

Patch by localheinz.

Closes php/doc-en#20.
 [2021-11-17 22:12 UTC]
Automatic comment on behalf of julionc
Log: Fix #20: SessionHandlerInterface - Different synopsis & examples not matching the synopsis
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun May 19 21:01:32 2024 UTC