Skip to content

[Bug] Incomplete cleanup of config.txt and conflicts after installing NoPspEmuDrm for ARK-5 cause GPU/CPU crashes. #309

Description

@Bluekey007

Hello,
I am reporting an issue regarding how AutoPlugin 2 handles the config.txt file during plugin installation and uninstallation, specifically involving the recent ARK-5 update.

When updating or removing plugins, the app sometimes fails to clean up properly. It leaves empty lines, duplicate paths, and leftover comments (for example, # vitabright and # itls) under the *KERNEL section.

Additionally, this problem became critical after installing the recently updated NoPspEmuDrm_kern.skprx module for ARK-5 via the app. The installation seems to disrupt the load order and corrupts the config file structure when combined with other plugins.

To Reproduce:

Install the NoPspEmuDrm mod for ARK-V (Acid_Snake) plugin and other kernel plugins via AutoPlugin 2.

Uninstall or update some of those plugins via the app interface.

Check ur0:tai/config.txt via VitaShell and notice the leftover blank lines, duplicate paths, and comments.

Expected behavior:
The app should cleanly remove all associated lines, including comments and blank spaces, to prevent taiHEN from misreading the file. It should also ensure that adding the ARK-5 module doesn't break the load order of other essential plugins.

Additional Context:
These leftover lines and messy formatting in the config.txt, combined with the integration of the new ARK-5 plugin, caused severe memory conflicts. In my case, it triggered random GPU/CPU crashes during heavy native Vita games (like Persona 4 Golden using rePatch). Manually removing the NoPspEmuDrm plugin and cleaning the empty lines and duplicate comments directly in VitaShell completely fixed the crashes and restored system stability.

07/03/2026
"Update: I have tested replacing the original rePatch with rePatch Reloaded, and the GPU crashes are significantly less frequent or non-existent in my current session. It seems the memory handling conflict between the original rePatch and the recent ARK-5/NoPspEmuDrm update was the primary cause. I will keep monitoring this, but for now, this workaround has stabilized the system."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions