The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm6 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm6 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm6 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb




SphereCommunity / Sphere 0.56d / General Help v / 56d Crash Bug


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
56d Crash Bug
Author Message
aserehe
Apprentice
*

Posts: 22
Likes Given: 1
Likes Received: 0 in 0 posts
Joined: May 2015
Reputation: 0



Post: #1
56d Crash Bug
Hi,

Crash bug on staff commands. I'm using .111 command than sphere loop this errors.

Compiled: Sep 27 2018 (07:29:31) [build 698 / Git hash 9e95d075]

01:32:1:Account 'admin' logged on char 'Admin' ('xxx.xxx.xxx.xxx')
01:32:1:'Admin' Says UNICODE 'ENU' '1' mode=0
01:32:1:'admin' commands '111'=1
01:32:DEBUG:__ thread (4228) __ | # | _____________ function _____________ | __ ticks passed from previous function start __
01:32:DEBUG:>> 4228 | 0 | CWorld::OnTick | +0
01:32:DEBUG:>> 4228 | 1 | CSector::OnTick | +0
01:32:DEBUG:>> 4228 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:32:DEBUG:>> 4228 | 3 | CChar::NotoSave_CheckTimeout | +0
01:32:CRITICAL:"Access Violation" (0xfff27710), in CChar::Tick() #2 "NOTO timeout"
01:32:DEBUG:__ thread (4228) __ | # | _____________ function _____________ | __ ticks passed from previous function start __
01:32:DEBUG:>> 4228 | 0 | NetworkManager::processAllInput | +0
01:32:DEBUG:>> 4228 | 1 | NetworkManager::checkNewConnection | +0
01:32:CRITICAL:"Access Violation" (0xffee7119), in Sphere::Tick() #4 "network-in"
01:32:DEBUG:__ thread (4228) __ | # | _____________ function _____________ | __ ticks passed from previous function start __
01:32:DEBUG:>> 4228 | 0 | NetworkManager::processAllInput | +0
01:32:DEBUG:>> 4228 | 1 | NetworkManager::checkNewConnection | +0
10-12-2018 08:40 AM
Find all posts by this user Like Post Quote this message in a reply
Coruja
Sphere Developer
*****

Posts: 987
Likes Given: 5
Likes Received: 226 in 187 posts
Joined: Jul 2012
Reputation: 7

Dimension Shard
Post: #2
RE: 56d Crash Bug
when you call functions only using numbers sphere will assume that the first value is an skill number and the second value is the skill value. So using ".12 50.0" as example, it will set cartography (skill 12) = 50.0 on the char

but the higher skill number is 57 (throwing), the skill 111 doesn't exist and sphere will just ignore it if you type ".111". So try check if your scripts have any kind of custom funcion named "111", probably this is creating a conflict with some internal sphere function
10-12-2018 10:51 AM
Find all posts by this user Like Post Quote this message in a reply
aserehe
Apprentice
*

Posts: 22
Likes Given: 1
Likes Received: 0 in 0 posts
Joined: May 2015
Reputation: 0



Post: #3
RE: 56d Crash Bug
No, i'm using default sphere script pack.

Latest SphereServer Script Pack
https://github.com/Sphereserver/Scripts/...master.zip
10-12-2018 05:42 PM
Find all posts by this user Like Post Quote this message in a reply
aserehe
Apprentice
*

Posts: 22
Likes Given: 1
Likes Received: 0 in 0 posts
Joined: May 2015
Reputation: 0



Post: #4
RE: 56d Crash Bug
Sphere crash are 108 109 110 111 and 112 commands.

Fix:
[f_oncommand]
for x 108 112
if (strmatch('<args>', '<local.x>'))
src.sysmessage Not a valid command
endif
endfor
10-14-2018 04:29 AM
Find all posts by this user Like Post Quote this message in a reply
Coruja
Sphere Developer
*****

Posts: 987
Likes Given: 5
Likes Received: 226 in 187 posts
Joined: Jul 2012
Reputation: 7

Dimension Shard
Post: #5
RE: 56d Crash Bug
sounds weird, I'm also testing on latest build with latest script pack

Code:
16:23:1:'admin' commands '105'=1
16:23:1:'admin' commands '106'=1
16:23:1:'admin' commands '107'=1
16:23:1:'admin' commands '108'=1
16:23:1:'admin' commands '109'=1
16:23:1:'admin' commands '110'=1
16:23:1:'admin' commands '111'=1
16:23:1:'admin' commands '112'=1
16:23:1:'admin' commands '113'=1
16:23:1:'admin' commands '114'=1
16:23:1:'admin' commands '115'=1
and the server still running fine

probably you should have something on your scripts conflicting with these internal functions, forcing sphere to create an infinite loop
10-16-2018 05:29 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)

Contact Us | SphereCommunity | Return to Top | Return to Content | Mobile Version | RSS Syndication