melonDS-android icon indicating copy to clipboard operation
melonDS-android copied to clipboard

Lag on S22 Ultra

Open UnveilingCoyote opened this issue 2 years ago • 20 comments

Emulator starts lagging minutes after starting a game

UnveilingCoyote avatar Jan 27 '23 14:01 UnveilingCoyote

Can you document what games you been trying to play, or if you have the DS BIOS, or the dsi mode

Littlemac123 avatar Feb 01 '23 02:02 Littlemac123

When will the lag be fixed

UnveilingCoyote avatar Feb 04 '23 19:02 UnveilingCoyote

With this information, there's nothing I can do. And the S22 is more than capable of running the emulator without issue. Make sure JIT is enabled in the "System" section in the settings. You can also try disabling sustained performance mode in the "General" section in the settings.

rafaelvcaetano avatar Feb 04 '23 22:02 rafaelvcaetano

When I play I get bad stuttering throughout, it won't stay at a constant 60fps affects new super mario Bros. Namco Museum DS, and Super mario 64 ds

UnveilingCoyote avatar Feb 06 '23 19:02 UnveilingCoyote

Hopefully in the future melonds software rendering will improve the performance. Screenshot_20230219_081655

ghost avatar Feb 19 '23 00:02 ghost

Here's some adb log

Entered adb shell
Success! ※\(^o^)/※
--------- beginning of system
--------- beginning of crash
--------- beginning of main
02-19 11:15:00.410 19260 19260 E AndroidRuntime: FATAL EXCEPTION: main
02-19 11:15:00.410 19260 19260 E AndroidRuntime: Process: me.magnum.melonds, PID: 19260
02-19 11:15:00.410 19260 19260 E AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 67108880 byte allocation with 25165824 free bytes and 28MB until OOM, target footprint 263838400, growth limit 268435456
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at la.c.a(Unknown Source:0)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at na.a.<init>(Unknown Source:18)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at la.j.<init>(Unknown Source:49)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at la.j.<init>(Unknown Source:4)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at la.j.<init>(Unknown Source:1)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at org.apache.commons.compress.archivers.sevenz.j.b(Unknown Source:12)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at org.apache.commons.compress.archivers.sevenz.g.a(Unknown Source:18)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at org.apache.commons.compress.archivers.sevenz.n.i(Unknown Source:89)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at org.apache.commons.compress.archivers.sevenz.n.G0(Unknown Source:40)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at org.apache.commons.compress.archivers.sevenz.n.j(Unknown Source:71)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at org.apache.commons.compress.archivers.sevenz.n.P(Unknown Source:43)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at f8.f.k(Unknown Source:0)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at f8.f.i(Unknown Source:22)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at f8.b.h(Unknown Source:38)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at f8.b.d(Unknown Source:6)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at t8.b0.g(Unknown Source:61)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at t8.b0.h(Unknown Source:11)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at t8.b0.b(Unknown Source:0)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at t8.b0$b.l(Unknown Source:37)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at e7.a.q(Unknown Source:11)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at u7.x0.run(Unknown Source:88)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at kotlinx.coroutines.internal.j.run(Unknown Source:12)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at kotlinx.coroutines.scheduling.k.run(Unknown Source:2)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at kotlinx.coroutines.scheduling.a.E(Unknown Source:0)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at kotlinx.coroutines.scheduling.a$c.d(Unknown Source:14)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at kotlinx.coroutines.scheduling.a$c.n(Unknown Source:28)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	at kotlinx.coroutines.scheduling.a$c.run(Unknown Source:0)
02-19 11:15:00.410 19260 19260 E AndroidRuntime: 	Suppressed: u7.v0: [k2{Cancelling}@b580f69, Dispatchers.Main.immediate]

ghost avatar Feb 19 '23 03:02 ghost

I'm on s20+ exynos and i am also seeing the slow down after a few minutes of play, i have installed a DS and DSi bios, DSi mode is turned off, JIT is turned on. I see it happen on Castlevania dawn of sorrow and on the DSi firmware. If I pause and unpause the emulation it returns to normal levels of performance for some time. Tested turning off treaded rendering to no effect.

LuanVSO avatar Feb 20 '23 19:02 LuanVSO

Any update on this?

UnveilingCoyote avatar Feb 28 '23 21:02 UnveilingCoyote

Any update on this?

Performance of this emulator will only improve if ever opengl renderer is implemented.

ghost avatar Mar 01 '23 00:03 ghost

When will this issue be fixed

UnveilingCoyote avatar Mar 06 '23 19:03 UnveilingCoyote

I don't have that specific device to be able to reproduce your problem. The closest thing I have is a Galaxy S10 and it doesn't suffer from the same problem. As such, you will have to be patient because addressing these things is not easy.

rafaelvcaetano avatar Mar 09 '23 18:03 rafaelvcaetano

Thank you Rafael for responding, I will wait.

UnveilingCoyote avatar Mar 09 '23 19:03 UnveilingCoyote

You can test apps on Samsung devices here for free: https://developer.samsung.com/remote-test-lab

LuanVSO avatar Mar 10 '23 11:03 LuanVSO

@rafaelvcaetano JIT doesn't work on my vivo y11 snapdragon 439 performance. I tried it disable/enable the fps doesn't change but the threaded rendering really helps.

Does JIT only optimize in higher specs devices?

ghost avatar Mar 15 '23 12:03 ghost

Performance is solid on 64 bit devices with thread rendering and JIT enabled, and should run at full speed on flagship devices. Performance on older devices, specially 32 bit devices, is very poor due to the lack of JIT support.

Maybe melonDS detected my phone as 32bit? What do you think about this?

But in DevCheck app my phone is 64bit supported. Screenshot_20230315_203553

ghost avatar Mar 15 '23 12:03 ghost

@rafaelvcaetano JIT doesn't work on my vivo y11 snapdragon 439 performance. I tried it disable/enable the fps doesn't change but the threaded rendering really helps.

Does JIT only optimize in higher specs devices?

Please open another issue

LuanVSO avatar Mar 15 '23 12:03 LuanVSO

It still slows down after a few minutes, please fix this

UnveilingCoyote avatar Aug 13 '23 15:08 UnveilingCoyote

Update on this?

UnveilingCoyote avatar Sep 25 '23 19:09 UnveilingCoyote

Could you stop pinging this thread? Everyone who is subscribed receives notifications when you do that. Besides that, annoying people will not get them any more inclined to fix this, especially because he has no obligation to do it

LuanVSO avatar Sep 29 '23 04:09 LuanVSO

Jeez, I didn't expect this kind of answer, I am sorry

UnveilingCoyote avatar Sep 29 '23 13:09 UnveilingCoyote