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-nmm7 (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-nmm7 (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-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ERROR Sphere 56d
Author Message
xtronchox
Apprentice
*

Posts: 24
Likes Given: 0
Likes Received: 0 in 0 posts
Joined: Mar 2020
Reputation: 0



Post: #1
ERROR Sphere 56d
I am having unexpected closures of Sphere without leaving any warning in console and it has me lost because it happens for no apparent reason. This error appears in the Windows Event Viewer. Does anyone have any idea what may be happening?

I am using this version of Sphere:

Sphere V0.56d-Nightly (32bit) by http://www.spherecommunity.net
Compiled at Mar 27 2020 (build 1040 / Git hash 413e9c5b)

And this is the error shown in the viewer:

Faulting application name: SphereSvr.exe, version: 0.56.4.1040, time stamp: 0x5e7e7a9c
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098858e
Exception code: 0xc0000005
Fault offset: 0x0002c733
Faulting process id: 0x304c
Faulting application start time: 0x01d64ae2d87b8136
Faulting application path: C:\SphereSvr\SphereSvr.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCR110.dll
Report Id: 174f6826-3f15-4cf4-83cd-e8d1ccf6df3f
Faulting package full name:
Faulting package-relative application ID:
(This post was last modified: 06-25-2020 10:33 PM by xtronchox.)
06-25-2020 10:31 PM
Find all posts by this user Like Post Quote this message in a reply
Lucas
Apprentice
*

Posts: 8
Likes Given: 0
Likes Received: 0 in 0 posts
Joined: Apr 2020
Reputation: 0



Post: #2
RE: ERROR Sphere 56d
I am having a similar crash too, no violation or error are reported on the console:

Faulting application name: SphereSvr.exe, version: 0.56.4.62766, time stamp: 0x5ef54b94
Faulting module name: ucrtbase.DLL, version: 10.0.14393.2990, time stamp: 0x5caeb859
Exception code: 0xc0000409
Fault offset: 0x000872b2
Faulting process id: 0x6d0
Faulting application start time: 0x01d6500707b4637a
Faulting application path: C:\shard\SphereSvr.exe
Faulting module path: C:\Windows\SYSTEM32\ucrtbase.DLL
Report Id: 0eb4c450-bc02-11ea-82f9-02292e4bb38a
Faulting package full name:
Faulting package-relative application ID:
07-02-2020 11:13 PM
Find all posts by this user Like Post Quote this message in a reply
xtronchox
Apprentice
*

Posts: 24
Likes Given: 0
Likes Received: 0 in 0 posts
Joined: Mar 2020
Reputation: 0



Post: #3
RE: ERROR Sphere 56d
From what I could find doing tests it has to do with the sphere collapse with the timers. I was using an item with timer = 1 and that timer was checking variables to jump events at a specific real time. Well, it seems that a timer jumping every second makes Sphere suffer. Set that timer to 40 (since the event will jump equal to the time I set it for as long as that minute.) And I have not had any crashes again.

If you read me any mod I would like them to explain the best way to set a timer for this purpose and that it is accurate.
07-03-2020 12:47 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


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