I see that's happening in the process of clearing an icon which has apparently been corrupted (at least, the 1204 error is), but unfortunately I don't have any information telling me how it got corrupted or what led up to it. A stack trace would be awesome; it's unfortunate Windows 7+ doesn't output that information.
| |
Upon further testing, it appears to be at least partially linked to others uploading icons into the environment. I started testing from some instances where I noticed others displaying icons to their friends while I was off-screen. I haven't been able to re-produce this while I am onscreen myself. There is a bit of delay between when they display the icon to when I crash.
EDIT: Nah, defiantly related to others displaying their uploaded icons off-screen. | |
I'd like to bump this, due to the fact it still happens to me. I'd really love to figure out a fix to this because its quite annoying.
| |
I'm not sure your issue was the same one first reported in this thread, as you had a hang, not a crash. Regardless, I've never been able to reproduce either one. I'll need more information from you about the hang, like which games this happens on. If Windows could detect what instruction offset in the program was last used (e.g., where it was in dreamseeker.exe, byondcore.dll, or byondwin.dll) when it figured out the app was hanging, that's something I could go on. Do you have the hang only in certain games or in certain conditions?
The best way to diagnose a hang of course is to attach a debugger. If there were an easy way you could do that and find out what part of BYOND was last accessed, that'd be a big deal. (With this hang, is the CPU also racing?) I understand if you haven't done this before it's not a trivial thing, so I can see if there's some info I can get you that will help. In any case I suggest you post a new bug report, because I don't think your issue is related to this thread. | |
Space Station 13, Dream Seeker in specific. And yes, it does make my CPU get pretty high around 80% at times and its a 3.2ghz quad core.
And I use Windows 7 Ultimate 64bit, it's a recurring problem and it happens to quite a few people I know but it doesn't happen on any other OS as far as I'm aware, just Windows 7 64bit. | |
Any word on the initial report, yet? It appears to be isolated to a very minor handful of clients uploading and displaying icons off-screen from a select few other clients; crashing their dreamseeker
| |
I still don't have a good set of steps to reproduce so I'm having to stab at this in the dark. How far offscreen does the other user have to be when the icon is uploaded? What kind of a delay are you talking about before the issue happens--seconds or minutes? As you can well imagine, this is very, very difficult to test.
The client garbage collector could be involved, but there's no way whatsoever for me to tell that without a stack trace. It would be a better culprit if I knew there were lots of objs being created and destroyed very frequently; in low-change environments, the garbage collector doesn't kick in very often. | |
It occurs whenever a object with a icon that has not been loaded into the resources and was uploaded by the player(which is the part I cannot reproduce, since it seems to depend on the player(ie: certain clients cause this to occur in every instance they display a non-cached icon out of view.)) is displayed anywhere outside of the view of the player. It happens within a couple of seconds, at most.
The next time this occurs and I'm able to trace it back to a player, I'll surely gather as much info on their connection as possible, as I've tried before to only have said player get hostile and refuse to answer. | |
Next time I see this I will try and grab the .dmi that is part of the crash. Not sure if it can help.
I have noticed that the crash won't happen if you are viewing the icon in any matter. As if it is displayed in a Stat panel it won't cause you to crash. Your client must not be able to view it in any way for it to crash you. Just something I have noticed. | |
Source: Application Error
Date: 9/11/2013 6:12:32 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: My-HP
Description:
Faulting application name: dreamseeker.exe, version: 4.0.499.1204, time stamp: 0x522ab7df
Faulting module name: byondcore.dll, version: 4.0.499.1204, time stamp: 0x522ab7a0
Exception code: 0xc0000005
Fault offset: 0x000564c9
Faulting process id: 0x850
Faulting application start time: 0x01ceaf32285b51d0
Faulting application path: C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll
Report Id: 40aa9caf-1b2f-11e3-b5be-d0df9ade3239
Event Xml:
1000
2
100
0x80000000000000
27602
Application
My-HP
dreamseeker.exe
4.0.499.1204
522ab7df
byondcore.dll
4.0.499.1204
522ab7a0
c0000005
000564c9
850
01ceaf32285b51d0
C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe
C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll
40aa9caf-1b2f-11e3-b5be-d0df9ade3239
_______________________________________
Log Name: Application
Source: Application Error
Date: 9/6/2013 11:00:41 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: My-HP
Description:
Faulting application name: dreamseeker.exe, version: 4.0.499.1202, time stamp: 0x5202ab71
Faulting module name: ntdll.dll, version: 6.1.7601.18205, time stamp: 0x51db9710
Exception code: 0xc0000005
Fault offset: 0x00038e19
Faulting process id: 0x1734
Faulting application start time: 0x01ceab73d3c70939
Faulting application path: C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: adfd5795-1769-11e3-b2f6-d0df9ade3239
Event Xml:
1000
2
100
0x80000000000000
27441
Application
My-HP
dreamseeker.exe
4.0.499.1202
5202ab71
ntdll.dll
6.1.7601.18205
51db9710
c0000005
00038e19
1734
01ceab73d3c70939
C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe
C:\Windows\SysWOW64\ntdll.dll
adfd5795-1769-11e3-b2f6-d0df9ade3239
_________________________________________
Log Name: Application
Source: Application Error
Date: 9/6/2013 10:41:41 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: My-HP
Description:
Faulting application name: dreamseeker.exe, version: 4.0.499.1202, time stamp: 0x5202ab71
Faulting module name: byondcore.dll, version: 4.0.499.1202, time stamp: 0x5202ab26
Exception code: 0xc0000005
Fault offset: 0x00055daa
Faulting process id: 0x3478
Faulting application start time: 0x01ceab592c534b2c
Faulting application path: C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll
Report Id: 06815ad5-1767-11e3-b2f6-d0df9ade3239
Event Xml:
1000
2
100
0x80000000000000
27439
Application
My-HP
dreamseeker.exe
4.0.499.1202
5202ab71
byondcore.dll
4.0.499.1202
5202ab26
c0000005
00055daa
3478
01ceab592c534b2c
C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe
C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll
06815ad5-1767-11e3-b2f6-d0df9ade3239
Got tons of these from the 6th.