search

FunkinCrew / Funkin

A rhythm game made with HaxeFlixel
https://www.newgrounds.com/portal/view/770371
Other
2.96k stars 2.29k forks source link

Bug Report: Game will freeze and say not responding when playing an extremely long song (4hr 18m) in the chart editor #3823

Open Shaunyman opened 1 day ago

Shaunyman commented 1 day ago

Issue Checklist

Platform

Itch.io (Downloadable Build) - Windows

Browser

None

Version

0.5.3

Description (include any images, videos, errors, or crash logs)

So, this is another issue that I have discovered while making and playing the marathon chart that I created. For anybody who is unaware, the marathon chart is an extremely long chart that combines all of the individual charts and difficulties into one massive chart (4hr 18 m long) that gets progressively longer as more songs are released for the official game. Making and testing it has spawned issues #3070, #3631, #3702, and #3822. #3070 has been fixed as of v0.5.0. Now it has spawned this issue, too. When being played in totality for the first time last night, it was discovered that the game will just straight up freeze and windows will say that the application is not responding even though the audio will continue to play and the chart will continue to advance until it starts working again. This chart also has to be played in the chart editor because of issue #3822, so this issue is currently only occurring in the chart editor. I will be testing this again on a different computer to see if the issue still occurs, but since my guess is that it will, I wanted to get this out there. Attached is the video of the issue occurring. It happened about 4 more times after this one and, since I haven't tested it anywhere else yet, am unsure if it happens at specific times in the chart or if it happens randomly. I will add a comment to this issue once I have tested it again to see if it happens at the same places, randomly, or not at all.

https://github.com/user-attachments/assets/3558c8f1-33cc-49d1-8fc7-4577c49197dc

Steps to Reproduce

Open and play a 4 hour long song/chart in the chart editor and the game may randomly stop functioning at certain points or random points. More testing is needed to see if it's random or at specific spots.

github-actions[bot] commented 1 day ago

Potential duplicates:

Shaunyman commented 1 day ago

Potential duplicates:

Wrong, bot!

EliteMasterEric commented 1 day ago

Surprised the 25 minute variation of this issue got fixed, does the game work fine with shorter tracks (like 3-4 hour ones?)

Anyway, marking as low priority since this is a rare issue to encounter.

Shaunyman commented 1 day ago

Surprised the 25 minute variation of this issue got fixed, does the game work fine with shorter tracks (like 3-4 hour ones?)

Anyway, marking as low priority since this is a rare issue to encounter.

I'm not too sure what you mean by 3-4 hour tracks since the track I used was just over 4 hours (4 hours 18 minutes and change). If you meant to say 3-4 minute ones, then no. Typically, because of the length of this chart, it's the one that finds all of the issues that nobody ever thought were possible. I will mention that the chart editor does stutter in charts of all length, though. Like it'll just stutter for a very short amount of time, but if you go to hit a note while it stutters, your input will not be registered and you'll miss the note. And, if you're holding a note when it stutters, you'll stop holding it when the stutter happens even if you never let go of the button. It's a separate issue, but might be related? I'm not sure

EliteMasterEric commented 21 hours ago

I'm not too sure what you mean by 3-4 hour tracks since the track I used was just over 4 hours (4 hours 18 minutes and change)

What I'm asking is at what point does the issue occur? Does it work when the track is only 4 hours and 0 minutes? What about only 2 hours? If it's fine at 2 hours then you can check at 3 hours, and keep subdividing until you find when the problems start becoming apparent.

Shaunyman commented 16 hours ago

I'm not too sure what you mean by 3-4 hour tracks since the track I used was just over 4 hours (4 hours 18 minutes and change)

What I'm asking is at what point does the issue occur? Does it work when the track is only 4 hours and 0 minutes? What about only 2 hours? If it's fine at 2 hours then you can check at 3 hours, and keep subdividing until you find when the problems start becoming apparent.

I see what you mean, now. I'm not sure and that's a good question. I'll do some testing and let you know. For reference, I'm using an audio file with a sample rate of 8000Hz for the chart because with too high of a sample rate, it'll begin to take literal minutes to load, and, with a sample rate too high, it will just instantly close the game. I posted that problem as issue #3702. I'll use 8000Hz for the sample rate with the subdivision testing I do as well and I'll post the results in a comment here.