Please report back after latest build.
Seems to have fixed it for me, good job! Thankspeppy wrote:
Please report back after latest build.
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GraphicsDevice'.
at Microsoft.Xna.Framework.InternalHelper.CheckDisposed(Object obj, Void* pComPtr)
at Microsoft.Xna.Framework.Graphics.GraphicsDevice.get_GraphicsDeviceStatus()
at #rb.#Hb.#wu()
at #rb.#Hb.#vu()
at #rb.#Hb.#mu()
at #rb.#xb.#4s()
at #rb.#xb.#7s()
at #rb.#xb.#it(Object , EventArgs )
at #rb.#Bb.#Dt()
at #rb.#Rb.#Sv(Object , EventArgs )
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.Control.WndProcException(Exception e)
at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at CallWindowProcW(IntPtr , HWND__* , UInt32 , UInt32 , Int32 )
at MouseSubClassFunc(HWND__* hWnd, UInt32 msg, UInt32 wParam, Int32 lParam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at #rb.#Rb.#ot()
at #rb.#xb.#ot()
at #1h.#np.#Iwb(String , Boolean )
It still happens with the same error on b20140323.4test.peppy wrote:
@Nathanael please test again on test build. I think I've fixed that case as well, but can't be sure.
=========================================TheVileOne wrote:
Reporting in that alt tabbing while a map is just starting prevents the HUD from loading and the map doesn't continue playing. You can still restart the map to get it to work.
Edit: I just softlocked the game when alt tabbing while Random was running. If you have trouble replicating, it softlocked at a point where the backgrounds hadn't loaded yet, and the loading circle over the leaderboards was visible. I'm not certain exactly how to reproduce it.
Alt tabbing over a map with no background breaks the user menu display.
Further weirdness caused by alt tabbing with F2
You can't fix it by yourself. Only the developers (or just peppy) can fix it.jose7952 wrote:
My osu crashes with Windows + D as well, please there's a way to fix this?
FYI, you'll still get 1 or 2 frames of extra latency on Windowed mode on Windows 8, even if you manage to turn off the forced vsync.Soinou wrote:
But well, if it's too hard to fix, nvm, i'll probably switch to windowed and find something to disable that horrible Windows 8 vsync.
[NM]NeverBack wrote:
bug game