We can noyt fix it : you ask a very big array with light memory.

I am aware, that you can't fix the underlying problem.
But there should be a way to fail more gracefully, shouldn't it?

For me as a server administrator some kind of message in the web-server logs are helpful. I suggest something in the line of what I did:
<pre>
--- framework/base/CApplication.php.orig 2016-06-08 16:44:14.364563000 +0200
+++ framework/base/CApplication.php 2016-06-08 16:55:19.674554000 +0200
@@ -197,6 +197,12 @@
*/
public function end($status=0,$exit=true)
{

• if ($exit === false) {
• $error = error_get_last();
• if(($error['type'] === E_ERROR) || ($error['type'] === E_USER_ERROR)) {
• error_log("A fatal error has occured: ". $error['message'] ." in file ". $error['file'] ." at line ". $error['line']);
• }
• }
  if($this->hasEventHandler('onEndRequest'))
  $this->onEndRequest(new CEvent($this));
  if($exit)
  </pre>

You are registering CApplication::end as a shutdown function in CApplication::run. So it gets called even on a fatal error and you can "handle" those errors...

OK,

Thne more a "beter log error" system.

Did you try with Yii error log system ? I think we must improve it.

But it's more a Feature request, not a bug. See the onEndRequest for the fix :)