The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined property: DB_MySQLi::$google_seo_query_limit - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Decrement on type null has no effect, this will change in the next major version of PHP - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once




i get crashes since "i don't know what revision"
#1
i don't know since when but every time my computer starts to lagg and my memory and/or disk is working 100% my MC-Server crashes. this happened in my self compiled R1001 and R1004.
http://www.mediafire.com/?022x67skb76j14n here is the pdb the crashdump etc.
Reply
Thanks given by:
#2
Try changing the fluid simulators from Floody to Classic, if it helps. I have a feeling the Floody simulator is still faulty and it definitely causes a lot of HDD and CPU action, because it floods large areas.
I'll have a look at the crashdump later in the day.
Reply
Thanks given by:
#3
but i was not doing anything with water.
Reply
Thanks given by:
#4
The crashdump doesn't say anything much, it is the small crashdump with almost no data other than the stack trace. So I know unloading a chunk failed, but the reason is in the stars. The big crashdump wouldn't have helped much, though, because this is probably a memory-overwrite issue - someone somewhere is writing in memory that doesn't belong to them. The hardest bug to find.
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)