[Bug]: The latest Asset Ripper builds crashes the Unity project.

[R5-3600]

Are you on the latest version of AssetRipper?

Yes, I'm on the latest alpha-build of AssetRipper.

Which release are you using?

Windows x64

Which game did this occur on?

Club Penguin Island
Windows version 1.13.0

Which Unity version did this occur on?

Unity 2017.4.12f1

Is the game Mono or IL2Cpp?

Mono

Describe the issue.

When I import the project to the Unity Hub, the project crashes.
I am using the following Asset Ripper settings:

Relevant log output

AssetRipper.log

[GZHYBFHHJ]

Can you send the Unity Editor log file after editor crashes?

[R5-3600]

Can you send the Unity Editor log file after editor crashes?

@GZHYBFHHJ, Editor.log

[R5-3600]

This issue also affects the latest v1.0.13 free and premium build of Asset Ripper.

[R5-3600]

Version 1.0.12 and older of Asset Ripper doesn't crash the Unity editor when I try to open the project.

[GZHYBFHHJ]

seems that AssetRipper messed something after a big changes commit
If I use Unity 2017.4 to open an exported project of a Unity 5.5.1 game, the out of memory popup shows when processing meshes (the editor tries to allocate 3GB VertexData memory. If I delete the mesh files, then it shows string oom popup when processing prefabs)
and in Unity 2021.3 games, the value of field m_DataSize in exported sprites is stored as hex data, not int32. It causes the Editor to keep allocating big memory (not only because it?)

[ds5678]

seems that AssetRipper messed something after a big changes commit
If I use Unity 2017.4 to open an exported project of a Unity 5.5.1 game, the out of memory popup shows when processing meshes (the editor tries to allocate 3GB VertexData memory. If I delete the mesh files, then it shows string oom popup when processing prefabs)
and in Unity 2021.3 games, the value of field m_DataSize in exported sprites is stored as hex data, not int32. It causes the Editor to keep allocating big memory (not only because it?)

Thank you for reporting, I see what you're talking about, and I am working on a fix.

[ds5678]

AssetRipper/AssemblyDumper@106b091 should fix the mesh issue you're experiencing. It'll make it into AssetRipper very soon.

[R5-3600]

seems that AssetRipper messed something after a big changes commit If I use Unity 2017.4 to open an exported project of a Unity 5.5.1 game, the out of memory popup shows when processing meshes (the editor tries to allocate 3GB VertexData memory. If I delete the mesh files, then it shows string oom popup when processing prefabs) and in Unity 2021.3 games, the value of field m_DataSize in exported sprites is stored as hex data, not int32. It causes the Editor to keep allocating big memory (not only because it?)

Ah. Thank you for testing that.

[R5-3600]

AssetRipper/AssemblyDumper@106b091 should fix the mesh issue you're experiencing. It'll make it into AssetRipper very soon.

That's good. Thank you.

[ds5678]

I just pushed a commit which should resolve the _typelessdata issue you were experiencing.

[GZHYBFHHJ]

Sprite issue is fixed
I haven't tried 5.5.1 one yet, but I think they are fixed too.

[ds5678]

Are you still experiencing the problem? Can this issue be closed?