View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001753SphereServerexecutable - genericpublic19-05-10 14:0522-01-11 05:27
ReporterIncanus 
Assigned ToMrSugarCube 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionnot fixable 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version0.56c Nightly 
Summary0001753: Client crashing when npc sitting on chair on border of clients visibility range
DescriptionUsing this function reproduces the crash for me each time

[function f_test_chair_crash]
go 5772,1872
serv.newitem 0121b
new.attr 010
new.p 5753,1873
serv.newnpc c_h_vendor
new.dir 3
new.p 5753,1873
go 5769,1869
Additional InformationOS: Windows
Build: r1280
UsePacketPriority doesn't make a difference
Crash didn't occur on September 2008 build
TagsNo tags attached.
Nightly VersionNot Available
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Attached Files

- Relationships

-  Notes
(0000485)
Incanus (reporter)
01-06-10 01:05

The issue was only fixed for the specific function I posted above. Here is a new, slightly modified one, that still crashes the client. Tested on r1291

[function f_test_chair_crash_new]
go 5772,1872
serv.newitem 0121b
new.attr 010
new.p 5753,1873
serv.newnpc c_h_vendor
new.dir 3
new.p 5753,1873
go 5769,1870
(0000856)
MrSugarCube (administrator)
22-01-11 05:27

I originally thought that the crash was related to the order that the 'item' and 'character' packets are sent in (and reverting them back to the same order as in the last prerelease at least fixed the original function). The second function however, still causes the crash even though the order is 'correct' (this function also produces the crash with the September 2008 build, and for extra confirmation I've reproduced the crash on other emulators as well).

At this point I can only conclude that the issue lies within the client itself. I have tested both functions using client 7.0.11.3 and the crash does not occur, so I would suggest updating to the latest client if possible.

- Issue History
Date Modified Username Field Change
19-05-10 14:05 Incanus New Issue
19-05-10 14:05 Incanus Nightly Version => Not Available
19-05-10 14:05 Incanus Experimental Flags => None
19-05-10 14:05 Incanus Option Flags => None
31-05-10 02:04 MrSugarCube Status new => resolved
31-05-10 02:04 MrSugarCube Fixed in Version => 0.56c Nightly
31-05-10 02:04 MrSugarCube Resolution open => fixed
31-05-10 02:04 MrSugarCube Assigned To => MrSugarCube
01-06-10 01:05 Incanus Status resolved => feedback
01-06-10 01:05 Incanus Resolution fixed => reopened
01-06-10 01:05 Incanus Note Added: 0000485
23-08-10 17:28 MrSugarCube Priority normal => high
22-01-11 05:27 MrSugarCube Note Added: 0000856
22-01-11 05:27 MrSugarCube Status feedback => closed
22-01-11 05:27 MrSugarCube Resolution reopened => not fixable


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker