StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There are a number of possible solutions ... depends on the "why" ... so it ends up being a bit of trial and error. On a fresh install, that's tricky to determine. But, if you made a recent "major" change that's a place to start looking - like modifying virtual hosts or adding/enabling XDebug.</p> <p>Here's a list of things I've used/done/tried in the past</p> <ul> <li><p>check for infinite loops ... in particular looping through a SQL fetch result which works 99% of the time except the 1% it doesn't. In one case, I was using the results of two previous queries as the upper and lower bounds of a for loop ... and occasionally got a upper bound of a UINT max ... har har har (<em>vomit</em>)</p></li> <li><p>copying the ./php/libmysql.dll to the windows/system32 directory (Particularly if you see <code>Parent: child process exited with status 3221225477 -- Restarting</code> in your log files ... check out: <a href="http://www.java-samples.com/showtutorial.php?tutorialid=1050">http://www.java-samples.com/showtutorial.php?tutorialid=1050</a>)</p></li> <li><p>if you modify PHP's error_reporting at runtime ... in certain circumstances this can cause PHP to degenerate into an unstable state if, say, in your PHP code you modify the superglobals or fiddle around with other deep and personal background system variables (Nah, who would ever do such evil hackery? <em>ahem</em>)</p></li> <li><p>if you convert your MySQL to something other than MyISAM or mysqli</p></li> </ul> <blockquote> <p>There is a known bug with MySQL related to MyISAM, the UTF8 character set and indexes (http://bugs.mysql.com/bug.php?id=4541) Solution is to use InnoDB dialect (eg sql <code>set GLOBAL storage_engine='InnoDb';</code>)</p> </blockquote> <ul> <li>Doing that changes how new tables are created ... which might <em>slightly</em> alter the way results are returned to a fetch statement ... leading to an infinite loop, a malformed dataset, etc. (although this change should not hang the database itself)</li> </ul> <p>Other helpful items are to ramp up the debug reporting for PHP and apache in their config files and restart the servers. The log files sometimes give a clue as to at least <em>where</em> the problem might reside. If it happens after your page content was finished it's more likely in the php settings. If it's during page construction, check your PHP code. Etc. etc.</p> <p>Hope the above laundry list helps somebody someday ... probably myself when I run into it again and come back here looking for "how the heck did I fix it last time?" ... :)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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