mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-04-24 21:56:10 +03:00
[GH-ISSUE #3301] Crashing if you set cpu speed to 1000 #1376
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#1376
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 @vsub on GitHub (Aug 21, 2013).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/3301
Don't know who will actually set it to 1000 but it crashes if you hit ok while 1000 is selected
Also if you manually set it to 1000,when you try to enter Game Settings=>System ppsspp will crash
@hrydgard commented on GitHub (Aug 21, 2013):
Hmm that's really bad.
Yeah, will have to do a 0.9.1 sooner than I expected...
@thedax commented on GitHub (Aug 21, 2013):
Call stack of the crash(it's the same crash for both ways of triggering it):
@thedax commented on GitHub (Aug 21, 2013):
Additional info: "Run-Time Check Failure #2 - Stack around the variable 'temp' was corrupted."
@vsub commented on GitHub (Aug 21, 2013):
It seems to be newui related
@thedax commented on GitHub (Aug 21, 2013):
Yes, I know.
@unknownbrackets commented on GitHub (Aug 21, 2013):
I'm sure the bug is here:
4 just isn't very long.
-[Unknown]
@thedax commented on GitHub (Aug 21, 2013):
Aha, that would explain it. Perhaps 32 would be more reasonable to allow room for growth?
@unknownbrackets commented on GitHub (Aug 21, 2013):
An unsigned 32-bit integer can be 10 characters long, so that'd be 11. But sure, 32 should be a nice reasonable safe value.
-[Unknown]
@thedax commented on GitHub (Aug 21, 2013):
Thanks for spotting that, @unknownbrackets.
@thedax commented on GitHub (Aug 21, 2013):
I think this can be closed now.