osu crash when importing beatmap #29413
Labels
area:import
dealing with importing of data from stable or file formats
realm
deals with local realm database
Comments
|
Try to re-export the logs. |
smoogipoo
added
missing details
|
i still can't do that even when i restart osu |
|
Weird. In that case... Open osu!, go into options, and click "open osu! folder", paste all the files from the |
|
it's corrupted and i can't read this |
|
Drag and drop the files directly here, you don't need to paste their content. |
|
i even can't zip that folder or drop folder here |
|
Okay, let's try a different way then... Check for any error logs in the event viewer (https://docs.microsoft.com/en-us/host-integration-server/core/how-to-check-the-windows-event-logs-for-errors1). |
|
Faulting application name: osu!.exe, version: 0.0.0.0, time stamp: 0x666b0000 |
|
Is there another error alongside that one listed as |
|
You might also have crashdumps under |
I only found that in event viewer |
|
osu!.exe.14992.dmp |
|
Thanks, that helps out a bit. Does this happen every time? Can you reproduce it by importing that beatmap? If so, then please also upload the At this point, it looks like it's an issue caused by Realm. I haven't seen this happen before but I am acutely aware we are stuck on the current version so there's nothing we can do right now except perhaps try to make a repro for the Realm devs to look into. Relevant stacktraces follows: osu!.exe.14992.dmposu!.exe.7492.dmp |
|
i retried with this beatmap but it still crash |
cc @peppy Something is broken in the database but I can't figure out what. Running that database locally, I get a native crash after the migration runs, of the form: At first glance this looks like potentially the migration is making duplicates, however I noticed that even if you make the migration a no-op (by removing all of its code), the same error will still occur after I went a little bit further and changed the migration to: HashSet<string> ids = new HashSet<string>();
testPrimaryKey<Guid>("Skin", "ID");
testPrimaryKey<Guid>("Score", "ID");
testPrimaryKey<string>("Ruleset", "ShortName");
testPrimaryKey<Guid>("ModPreset", "ID");
testPrimaryKey<Guid>("KeyBinding", "ID");
testPrimaryKey<string>("File", "Hash");
testPrimaryKey<Guid>("BeatmapSet", "ID");
testPrimaryKey<Guid>("BeatmapCollection", "ID");
testPrimaryKey<Guid>("Beatmap", "ID");
void testPrimaryKey<T>(string objectName, string pkColumn)
{
ids.Clear();
foreach (var item in migration.OldRealm.DynamicApi.All(objectName))
{
if (!ids.Add(item.DynamicApi.Get<T>(pkColumn)!.ToString()!))
{
Trace.Fail("This should not be reached.");
}
}
}And the trace is never hit - realm still crashes with the supposedly duplicate PK. Sounds like some dark magic at play here - perhaps disk corruption or something as above. I'm not sure what the resolution is here. |
|
Realm discussion thread: realm/realm-core#7988 |
peppy
added
realm
|
I've attempted to fix your corrupt database: I can't guarantee that this will continue to work forevermore and there may be a time where you'll have to start over from scratch, but it may be enough for now... |
|
i'm using cpu intel pentinum gold g6400. and i think it doesn't power outage (it's using 10W when opening osu), no crash system crash when open osu |
|
Realm has applied a fix to the database themselves, which is likely (definitely) better than my fix. I recommend using it: |
|
it's worked, thanks |
|
my osu can't open after some week after this issue, and i checked event log and i saw it come from realm file. so i replace it by |
|
I'd propose starting from a new database at this point. |
|
how i can do that? |
|
And is there anyway to recorer my beatmaps i imported in the osu data folder without realm database? |
|
There would not be a way to recover, no. |
|
thank |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type
Crash to desktop
Bug description
When i tried to download this beatmap and then open it, osu doesn't open. Then i tried inport that beatmap in the game but when i press import it still crash.
Screenshots or videos
No response
Version
2024.731.0-lazer
Logs
i can't export my log, this file might not right
1723615488.nauth.log
The text was updated successfully, but these errors were encountered: