-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
N.O.V.A. Mini causing crash in intro #3485
Comments
http://report.ppsspp.org/logs/game/NPEZ00222_1.02 I implemented sceKernelCancelMutex recently. Have you tried the latest build? -[Unknown] |
Downloading ... |
still crashing on v0.9.1-289 0n android! |
Yes it is still crashing |
Here is the log from 309 https://docs.google.com/file/d/0B3rTyJJIiCCZUVlKVXU0SUFYM0E/ |
Any change with this game? -[Unknown] |
Still crashing at same place |
tried with 1954 same result |
Any improvement? If not, does anyone have a debugger they could get a stack trace with? -[Unknown] |
@unknownbrackets |
Qt is fine too as long as it crashes there. I just want a stack trace. -[Unknown] |
Any change? There's video stuff nearby so maybe it was affected by recent changes in that area. -[Unknown] |
No changes. video is not causing it |
So, I think the problem here may be that the game tries to free old (already freed) pointers in a way that works on the PSP, but not in PPSSPP. The reason is we currently have different allocation semantics. If it affects this game (assuming I'm right), it can affect others... The PSP maintains a freelist and uses 8-byte blocks for allocation. Here's how it basically looks: struct VplBlock {
VplBlock *next;
u32 sizeDiv8;
};
struct VplHeader {
void *start;
void *startAgain;
void *startPlusSeven;
u32 totalSizeMinus8; // or offset of last block?
u32 allocatedDiv8;
VplBlock *nextFreeBlock;
VplBlock bottomBlock;
}; The VplHeader is found at the start of the vpl (the first 0x20 bytes which are not allocatable.) Going from the bottom upward, it's easy enough to list all blocks using Currently, we always allocate from the top down. This means we more eagerly reuse blocks than a freelist algorithm would. This may fragment memory better (providing more contiguous free blocks), depending on usage, but is also slower. So I guess we could try changing the allocation strategy. I've also tried to implement SMALLEST, and found bugs in our current allocation prioritization (namely, the most common method, FIFO, was treated as SMALLEST.) But further looks at logs to this game revealed that it only allocates from one thread, so it probably doesn't matter. -[Unknown] |
Ugh. Oh well, I've gone ahead and implemented it (not try yet, or I have a bug if it does use the same algorithm...) I'm pretty sure it'll be faster for Pangya, probably. Let's hope it helps this game. -[Unknown] |
Emulator crashes when press start menu appears
http://forums.ppsspp.org/showthread.php?tid=293&pid=45902#pid45902
Log file
http://forums.ppsspp.org/attachment.php?aid=6894
The text was updated successfully, but these errors were encountered: