forum

[resolved] [confirmed] osu! crashing when exiting from spectator mode.

posted
Total Posts
32
Topic Starter
Marcin
If you try to watch, someone who is watching someone else playing (in this case I was checking CtB), and if you exit shortly after getting forwarded, osu! crashes.
Crash details: http://db.tt/6aW35qpi

Steps to reproduce:
1. Find someone, watching someone else playing a game.
2. Try to spectate them
3. Quickly exit shortly after spectating begins (when you'll be seeing actual gameplay).
4. Enjoy broken sound, and osu! pippi crash.

On 4 tries, crashed 3 times.
Edit: Seems to happen randomly, or at least - there is one more thing causing this, because on some players I'm able to crash, but on some - not.

This time not useless report ;_;
TheVileOne
I triggered it after exiting after several fruits were caught. The OP tells me there are other ways to trigger it as well. The error message says Attempted to read Protected Memory.
Topic Starter
Marcin
I've also triggered it while testing with TVO by rapidly changing spectators - seems to be related to spectating as a whole, not just chains.
Edit: Video:
TheVileOne
I'm getting it by unspectating and then respectating the same user. After awhile it will just trigger and crash the game. Having the user catch some fruit and then escaping is triggering the crash as well.
peppy
I'm not getting this crash reported to my crash logs, so if possible could you please copy and paste the content of the "details" tab on the crash dialog.
Topic Starter
Marcin
System.AccessViolationException: There was attempt to read / save a protected memory region. It often means that the memory could be broken (idk how to translate it better)
peppy
The details tab (second tab) should contain more than just this. I need that.
Topic Starter
Marcin
It's shown on video - there is nothing more.
*or i'm so blind, but I don't think i'm that dumb*
TheVileOne


This is all it shows.

I should note that the game doesn't crash. It just throws this error that forces you to exit the game.


Perhaps your error reporting in this part of the game isn't as robust. If my memory serves me well, this type of error has never came with a list of methods with it. It used to happen while dealing with Timing lines in the editor. It doesn't anymore thankfully.
Topic Starter
Marcin
Also, there is a link for screenshot in the OP, but peppy didn't look up :(
PrivatHansi1
well i am using this settings:


and it happend to me 3 times in a row, BUT i was watching one person and i didnt speced another one.
never happend before, maybe one of the last patches caused this problem
MouseOnly25
I have the same problem, i started spectating a player and then i switch to another during playing..

MillhioreF
Spectating 3-5 CtB players in a row seems to cause this. It's gotten worse now, though - it simply displays "osu! has stopped working" instead of the custom error dialog.

Edit: One of the osu.exe threads seems to be locking and infinite looping. Posting a stacktrace on the off chance it'll help (probably not)
box
0, ntoskrnl.exe!_misaligned_access+0x17e7
1, ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
2, ntoskrnl.exe!KeWaitForMutexObject+0x19f
3, ntoskrnl.exe!_misaligned_access+0xba4
4, ntoskrnl.exe!_misaligned_access+0x1821
5, ntoskrnl.exe!_misaligned_access+0x1a97
6, mscorwks.dll!DllRegisterServerInternal+0x4193
7, 0xc2b4f148
8, 0x7b568c0018e94c
9, 0x735e146e7358d338
10, 0x18e94cc2b4f150
11, 0x18e924002ec900
12, 0x2ec96410208f10
13, 0x18e680003a1340
14, 0x10208f10735994d7
15, 0x18e6f400000034
16, 0xef516800fc32b95
17, 0x300018e710
18, 0x10208f100018e710
19, 0xfc32c040018e6f4
20, 0xfc3426800000000
21, 0x18e74000000000
22, 0x18e78c
23, 0x18e6dc00000001
24, 0x6f6b19f400000000
25, mscorwks.dll!DllRegisterServerInternal+0x4193
26, mscorwks.dll!CorExitProcess+0x158f4
27, mscorwks.dll+0x1daa
28, 0x3da056
29, 0x59d5a5f
30, 0x59d3a3b
31, System.Windows.Forms.ni.dll+0x20bcb7
32, System.Windows.Forms.ni.dll+0x208ddf
33, System.Windows.Forms.ni.dll+0x208957
34, System.Windows.Forms.ni.dll+0x2087a1
35, System.Windows.Forms.ni.dll+0x1c5911
36, mscorwks.dll+0x1b4c
37, mscorwks.dll+0x18951
38, mscorwks.dll!CoUninitializeEE+0x11861
39, mscorwks.dll!CoUninitializeEE+0x11894
40, mscorwks.dll!CoUninitializeEE+0x118b2
41, mscorwks.dll!StrongNameErrorInfo+0xfd81
42, mscorwks.dll!StrongNameErrorInfo+0xfca1
43, mscorwks.dll!StrongNameErrorInfo+0x101be
44, mscorwks.dll!CorExeMain+0x168
45, mscorwks.dll!CorExeMain+0x98
46, mscoreei.dll!CorExeMain+0x71
47, mscoree.dll!CreateConfigStream+0x13f
48, mscoree.dll!CorExeMain+0x8
49, ntdll.dll!RtlInitializeExceptionChain+0x63
50, ntdll.dll!RtlInitializeExceptionChain+0x36
peppy
I still can't replicate this. It must require very specific conditions..
Eni
Re: t/147515

I have the same issue but that was my first time spectating someone after restarting. I was not pressing any keys when the crash occurred.
Kaguya Hourain

Project Railgun wrote:

Re: t/147515

I have the same issue but that was my first time spectating someone after restarting. I was not pressing any keys when the crash occurred.
I got that as well now. Client suddenly crashed after player switched maps. I went to spectate another person afterwards but I didn't get crash again. Must be between certain maps or something from what I assume. Still testing.

*EDIT* Tried spectating the same songs in a row, I didn't crash. Something else must be the cause that is escaping me right now.
peppy
I've found the cause of this, and am working on a fix. It's about the worst thing that can possibly go wrong (managed code collecting an unmanaged callback function while it is still being called by a no-longer-referenced unmanaged object).
peppy
Should be fixed in the next release.
Topic Starter
Marcin
Is it already pushed to public? because http://db.tt/gMtYllDv
Jesss
I got this error...i just said "WAT?"

My case is pretty "unique" and kinda rare ._. I was about to find a song to play via "search" and the music suddenly started to sound like a damaged CD (endless loop) and the Pippi window appeared with the "system.accessviolationexception: attempted to read or write protected memory. This is often an indicating that other memory is corrupt" error and no debug info appeared O_O. However, the game didn't freeze at all.

Here my Screenshot



My settings:

show more
Please sign in to reply.

New reply