Project

General

Profile

Actions

Emulator Issues #12316

closed

Android: Dolphin crashes before games even boot,gfx errors logged.

Added by retroben about 4 years ago. Updated about 4 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
Android
Issue type:
Bug
Milestone:
Regression:
Yes
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
5.0-12958
Fixed in:
5.0-13001

Description

Issue is not present in 5.0-12956 and happens in 5.0-12958.

I did the most basic things to run a game on the working build and it boots Twilight Princess just fine on at least the warning screen before the title screen.
Doing the same basic steps of adding a directory to pick a game on 5.0-12958 and 5.0-12964 (before testing Gecko code support fix in that build itself) then attempting to run the game and other games ends up with a "has stopped" error promptly before it closes the app.
I had also tested a fresh install with new folder creation on 5.0-12964,so its not my files causing it.

OpenGL alleged problem log entry from 5.0-12958;

25:46:497 ../../../../../../Core/VideoBackends/OGL/Render.cpp:763 W[Video]: Missing OGL Extensions: PinnedMemory

Vulkan (supposedly swapchain);
No visible gfx/video related errors in log this time,yet still crashing out with "has stopped" error,audio was stopped as an error though.

Vulkan's log details from 5.0-12964;

51:21:547 ../../../../../../Core/VideoBackends/Vulkan/VulkanContext.cpp:458 I[Video]: Enabling extension: VK_KHR_swapchain
51:21:633 ../../../../../../Core/VideoBackends/Vulkan/VulkanLoader.cpp:220 E[Video]: (CreateSwapChain) vkCreateSwapchainKHR failed: (-1000000000: VK_ERROR_SURFACE_LOST_KHR)
51:21:633 ../../../../../../Core/Common/MsgHandler.cpp:115 E[MASTER]: Question: Failed to create Vulkan swap chain.
51:21:643 ../../../../../../Core/Common/FileUtil.cpp:138 I[COMMON]: Delete: file /storage/emulated/0/Android/data/org.dolphinemu.dolphinemu/cache/Shaders/Vulkan-Pipeline-6FFF40.cache

Hopefully this can be fixed fairly quickly so that I can test if another issue (Gecko codes triggering crash) is actually fixed on my end.

Actions #1

Updated by JosJuice about 4 years ago

  • Regression changed from No to Yes
  • Regression start set to 5.0-12958
  • Operating system Android added
  • Operating system deleted (N/A)
Actions #2

Updated by JosJuice about 4 years ago

Thanks for bisecting.

The log messages you posted might not actually be related to the issue. That doesn't make me any wiser about what's causing this issue, though... It works on my phone, so I can't reproduce it in a debugger.

Actions #3

Updated by retroben about 4 years ago

I get the same "Missing OGL Extensions: PinnedMemory" from 5.0-12956 and it boots fine.

How do I squeeze out the most information possible from Dolphin for use on checking the crashing build?

Actions #4

Updated by JosJuice about 4 years ago

The way I like the most personally is running the app using the "Debug" command in Android Studio and seeing where in the code it crashes, but that's cumbersome if you don't already have an Android Studio install. I wonder if there's some lightweight way to just see logcat info from the device without having to install too much on your PC...

Actions #5

Updated by jjLDN about 4 years ago

By the description of the issue I'm having exactly the same on my nVidia Shield TV for several days, however in my case the last working revision is 12954. On my android phone all works fine.
On Shield in logs I'm getting this:

11:21:429 ../../../../../../Core/Common/FileUtil.cpp:223 I[COMMON]: CreateFullPath: path exists /storage/emulated/0/dolphin-emu/Dump/Textures/
11:21:429 ../../../../../../Core/Core/ConfigManager.cpp:346 I[BOOT]: Loading Settings from /storage/emulated/0/dolphin-emu/Config/Dolphin.ini
11:21:431 ../../../../../../Core/Common/FileUtil.cpp:412 I[COMMON]: ScanDirectoryTree: directory /storage/emulated/0/dolphin-emu/Load/DynamicInputTextures/
13:12:929 ../../../../../../Core/Core/IOS/IOSC.cpp:564 W[IOS]: keys.bin could not be found. Default values will be used.
13:12:024 ../../../../../../Core/Core/ConfigLoaders/BaseConfigLoader.cpp:78 N[CORE]: Disabling WC24 'standby' (shutdown to idle) to avoid hanging on shutdown
13:12:111 ../../../../../../Core/Core/IOS/IOSC.cpp:564 W[IOS]: keys.bin could not be found. Default values will be used.

I have even reseted my Shield to factory settings to make sure there is nothing else running or interrputing Dolphin in any other way.
No idea, what else I can do to investigate this issue further.

Actions #6

Updated by JosJuice about 4 years ago

5.0-12956 made a change related to devices that don't have touchscreens. retroben, does your device have a touchscreen?

Actions #7

Updated by retroben about 4 years ago

Forgot to mention on this issue that it is Shield TV that I am on like for the cheat crash issue,seeing as how it is a follow-up issue from me not being able to test the Gecko codes fix due to this crashing problem without and codes enabled.

I remember on a quite old version of Dolphin,it would crash if I tried to open an extra menu by pressing the physical menu button,and when I attempted to load the controller buttons overlay,it would trigger a crash.
Could the controller overlay be attempting to load by default despite being on my Shield TV and thus trigger the crash?

(It could of been some other option I selected from the extra menu on the bottom of the screen,its been so long that I don't remember)

And just a heads up,I also just tried 5.0-12999 and it still crashes immediately when trying to open a game.

Actions #8

Updated by JosJuice about 4 years ago

Ah, I see now how 5.0-12958 would cause issues when the overlay controls are not loaded. Please check if this build fixes the problem: https://dl.dolphin-emu.org/prs/82/7d/pr-9243-dolphin-latest.apk

Actions #9

Updated by jjLDN about 4 years ago

Works for me. This build allows games to start and run just fine. :)

Actions #10

Updated by JosJuice about 4 years ago

  • Status changed from New to Fixed
  • Fixed in set to 5.0-13001
Actions #11

Updated by retroben about 4 years ago

Can confirm this fixed it for me with 5.0-13001 on my end as well.

Actions

Also available in: Atom PDF