Could this possibly be part of the issue?
The GZIP and Mp3PspThreads use the exact same entrypoint 0x08a5a278(not to mention different stack sizes, though that can be normal)...doesn't that seem odd for a music thread and a compression thread to have the exact same beginning?
Code:
30:28:500 user_main I[HLE]: HLE\sceKernelThread.cpp:1933 1614=sceKernelCreateThread(name=GZIP, entry=08a5a278, prio=11, stacksize=8192)
30:28:500 user_main I[HLE]: HLE\sceKernelThread.cpp:1976 sceKernelStartThread(thread=1614, argSize=4, argPtr=09fff5b0)
35:00:033 user_main W[HLE]: HLE\sceMp3.cpp:307 UNIMPL: sceMp3InitResource
35:00:063 user_main I[HLE]: HLE\sceKernelThread.cpp:1933 1626=sceKernelCreateThread(name=Mp3PspThread, entry=08a5a278, prio=10, stacksize=16384)
35:00:063 user_main I[HLE]: HLE\sceKernelThread.cpp:1976 sceKernelStartThread(thread=1626, argSize=4, argPtr=09fff4e0)The GZIP and Mp3PspThreads use the exact same entrypoint 0x08a5a278(not to mention different stack sizes, though that can be normal)...doesn't that seem odd for a music thread and a compression thread to have the exact same beginning?
4GHz AMD 3900X, 32GB DDR4 RAM, 6GB Nvidia RTX 2060, Asus Crosshair 7 Hero (Wifi), Linux
How to ask useful questions: https://web.archive.org/web/20110214010944/http://support.microsoft.com/kb/555375
I'm not Dark_Alex, nor do I claim to be. Our nicknames are merely coincidence.
How to ask useful questions: https://web.archive.org/web/20110214010944/http://support.microsoft.com/kb/555375
I'm not Dark_Alex, nor do I claim to be. Our nicknames are merely coincidence.

