Any Ideas what this is?

Fatal error: Call to a member function check() on a non-object in /inc/classes/BxDolTwigModule.php on line 964

Line 964

if($aItem[$this->_oDb->_sFieldStatus] == 'approved' && $aParams['obj_privacy']->check($aParams['txt_privacy_view_event'], $iId, $this->_iProfileId))
                $aItems[] = $aItem;

It seems your DB was unavailable, unless this is new code that is trying to reference an object that is not available, a bug

It did go away...Hmmm

The forums are filled with these. They are normally not code problems. Normally these errors are caused by things like the database server timing out, or not responding fast enough.

The forums are filled with these kinds of things because most people are on very cheap under powered servers they are trying to run dolphin on. Common on shared hosting. On a good server, these are rare. I have yet to ever see it myself, but then again, my server is not currently in heavy use.

I'm on shared hosting with Zarconia but never have that problem. I love their top notch services, would recommend all to use Zarconia to keep them in business for a long long time so I can enjoy their services.

 I have my ded with them.

The shared is good also. I had one of those as well. The bandwidth restrictions were to low for my needs. Thats the only issue i had. Yes, the servers they use are good, and properly configured which is why they run well.

I was referring to the many hosts out there that are not properly configured. Do not meet all of dolphins requirements. There are many, and is the cause of a lot of the issues i see reported in the forums.

In most cases the issue is related to memory management and the lack of available memory for joins. This can be because of  lack of memory, or badly implemented joins (the working set the join is based is too large) or missing limits (like in the forums) To solve this last issue you should start with pagination in the forums.

Well I have a very fast dedicated server with tons of memory through HostGator.  They have had issues lastly with their Provo server stations!  

 You can have tons of memory but if MySQL is not allowed to use it...