mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-04-25 14:16:10 +03:00
[GH-ISSUE #1253] Fonts cause black screens if they don't exist in homedir on Linux #400
Labels
No labels
Atrac3+
Audio
CPU emulation
D3D11
D3D9 (removed)
Depth / Z
Feature Request
Font Atlas
GE emulation
Guardband / Range Culling
HLE/Kernel
I/O
Input/Controller
MP3
Multithreading
Needs hardware testing
Networking/adhoc/infrastructure
No Feedback / Outdated?
OpenGL
PGF / sceFont
PSMF / MPEG
Platform-specific (Android)
Platform-specific (Windows)
Platform-specific (iOS)
PowerVR GPU
SDL2
Saving issue
User Interface
Vulkan
arm64jit
armjit
armv6
x86jit
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ppsspp#400
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chaserhkj on GitHub (Apr 11, 2013).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/1253
Met with segmentation fault while trying to load some translated AVG games.
This behavior was observed in loading of Toradora Portable (Chinese Translated version) and Ore no Imouto ga Konnani Kawaii Wake ga Nai Portable (Chinese Translated Version) these two games.
Error output file:
https://docs.google.com/file/d/0B2cmIAqfPwVaZ2lGZUkzSURwYTQ/edit
I'm not sure what module of the app caused this bug, but I suppose it is about the fonts... And it may even be something with the Chinese translated version's problem, which may use GBK encoded fonts rather than UTF8. But as I haven't got any original Japanese game isos, I cannot test it myself to locate the problem.
@unknownbrackets commented on GitHub (Apr 11, 2013):
Is this with fastmem off? Do you have a compiler you could use to get a stack trace (such as Visual Studio Express)?
-[Unknown]
@chaserhkj commented on GitHub (Apr 11, 2013):
@unknownbrackets
Opps, I ran the game with fastmem on....
Turning fastmem off actually clears the crash of the whole program, but the game still won't work, it blocks with a black screen, here is the error output:
https://docs.google.com/file/d/0B2cmIAqfPwVaV3l5X0EtSXptUjA/edit?usp=sharing
I tried the gdb with debug build under Linux platform, send a sigint while the app is blocked ,and get the following stack trace info:
1 0x000000000067b642 in FramebufferManager::CopyDisplayToOutput (this=0xfb4de8) at /home/hkj/ppsspp/GPU/GLES/Framebuffer.cpp:468
2 0x00000000006786d4 in GLES_GPU::CopyDisplayToOutput (this=0xfb2190) at /home/hkj/ppsspp/GPU/GLES/DisplayListInterpreter.cpp:273
3 0x00000000005a65f0 in hleEnterVblank (userdata=345, cyclesLate=2) at /home/hkj/ppsspp/Core/HLE/sceDisplay.cpp:400
4 0x0000000000597903 in CoreTiming::ProcessFifoWaitEvents () at /home/hkj/ppsspp/Core/CoreTiming.cpp:479
5 0x0000000000597a53 in CoreTiming::AdvanceQuick () at /home/hkj/ppsspp/Core/CoreTiming.cpp:520
6 0x0000000000597b05 in CoreTiming::Advance () at /home/hkj/ppsspp/Core/CoreTiming.cpp:543
7 0x0000000040100025 in ?? ()
8 0x0000000000000000 in ?? ()
Updated issue name.
@unknownbrackets commented on GitHub (Apr 11, 2013):
Hmm, "libc:%s: no reent structure", that's never a good thing (that's coming from the game's libc.) It does look probably font related as you said.
-[Unknown]
@chaserhkj commented on GitHub (Apr 13, 2013):
After copying all the font files from ppsspp/flash0/font/ to my ppsspp flash path ~/.ppsspp/flash, this font related problem is solved, PPSSPP still have other problems while running these AVGs, but that would be another issue.
Also, I recommend that we should add some code to initialize user's flash directory with flash0 directory or at least add some instructions in docs, do some packaging for linux users about these fonts. But I think these would be other issues, too.
Anyway, I think this issue can be closed.
@unknownbrackets commented on GitHub (Apr 13, 2013):
I'm going to reopen and edit the title of this issue, we should handle this better.
-[Unknown]
@unknownbrackets commented on GitHub (Oct 27, 2013):
This has been done now, it copies them into the build directory and uses them from there.
-[Unknown]