Databases
StackOverflow2013
Postsdbo
POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
    primarykey
    data
    text
    <p>I have a PHP function that is getting data from an SQL DB. Sometimes I get this fatal error while doing odbc_result</p> <ul> <li>Step 30 from 60 | Memory 191908 </li> <li>Step 31 from 60 | Memory 191908 </li> <li>Step 32 from 60 | Memory 191908 </li> <li>Step 33 from 60 | Memory 191908 </li> <li>Step 34 from 60 | Memory 191892 </li> <li>Step 35 from 60 | Memory 191908 </li> <li>Step 36 from 60 | Memory 191908 </li> <li>Step 37 from 60 | Memory 191892 </li> <li>Step 38 from 60 | Memory 191908 </li> <li>Step 39 from 60 | Memory 191908 </li> <li>PHP Fatal error: Out of memory (allocated 262144) (tried to allocate 4294967293 bytes)</li> </ul> <p>This is a piece of my output from the function.</p> <p>Can someone please help me with this problem?</p> <pre><code> while(odbc_fetch_row($exec_query_tblKlantFactuurOpdrachten)) { $dataADDRow_1 = $doc-&gt;createElement("tblKlantFactuurOpdrachten"); $dataADDRow-&gt;appendChild($dataADDRow_1); $i_1 = 1; while($i_1 &lt; $numFields_1) { echo "Step ".$i_1." from ".$numFields_1." | Memory ".memory_get_usage()."\n"; $dataFromDB = odbc_result($exec_query_tblKlantFactuurOpdrachten,$i_1); $dataADD = $doc-&gt;createElement($tmpArr_FieldName_1[$i_1],protectInfo($dataFromDB)); $dataADDRow_1-&gt;appendChild($dataADD); flush(); ++$i_1; } flush(); } </code></pre> <p>I've retried to get the data from the DB with a simple query and when i try to get the same exact field I get that error also. So it seems that is something with the relationship between DB and PHP. I am using freetds driver on linux server.</p> <p>When I get the data with SQL Server Management there is no problem.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdam Lear
    1. USandy1786
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
      1. This table or related slice is empty.
      1. VTDownMod
    1. CO`tried to allocate 4294967293 bytes` --- O_o
      singulars
      1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
      1. USzerkms
    2. COThat looks like a loop in your code. Allocating 4GB of memory shouldn't be necessary for your application, i guess. What's in that database, and how is that query looking?
      singulars
      1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
      1. USAlp
    3. COthe data is too big and.....your server is running out of memory. increase it or optimize your query. I suggest the latter.
      singulars
      1. POPHP fatal error - out of memory - tried to allocate 4294967293 bytes
      1. UStradyblix
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload