usymtool is eating up all my RAM

Every time I run my game in the device through xcode, multiple usymtool processes (over 10) start, eating up all my RAM memory:



I always have to kill the processes.
I'm using xcode 9.2, Unity 2018.3.0f2 and macOS 10.12.6.

What's usymtool and why does this happen?

 

Having exactly the same issue, anyone knows what this is?

 

Can you try upgrading XCode?

 

I’d have to upgrade macOS and I think my Mac can’t handle it

 

Doing a Purge while creating the build worked for me, using this command on the terminal "sudo purge" i also created the script as suggested on this website to run it easier:

https://mac-how-to.gadgethacks.com/how-to/speed-up-your-mac-2-minutes-flat-0166928/

 

I have same issue, I am using xcode 10.2.1, mac os 10.14.5, unity 2019.1.14. Any solution for this?

 

This is super annoying.
Is anyone looking at this? Happening with Unity 2019.2.0f1.
Any ideas besides killing all the processes? It also seem to not happen every time.

Quickest way I've found is to just run `killall usymtool` in the terminal.

 

Having the same problem! Are there any solutions yet besides killall?

 

Also experiencing this for the past few days, and

sudo purge

doesn't seem to resolve it.

 

Well, I updated the tvOS version on the device, and the problem seems to have resolved itself. Either that, or it was a result of completely deleting the Xcode build folder that was output by Unity. Hoping I can replicate the fix using one of those two methods in the future, if it crops up again.

 

Yup, definitely seems like deleting the Xcode project folder contents does the trick.

 

I have same issue in my Mac. It's really annoying! Please fix it soon. I use Unity 2018.4.9 and Xcode 10.3 on Mac Mojave 10.14.6. usymtool and lzma always eat all ram when I build app in Xcode

 

For reference though, this does seem excessive...

 

Seems to happen randomly too. Usually doing a "Replace" instead of "Append" on your next build will fix it temporarily

 

But that is really inconvenient when you always have to edit info.plist every time you build

 

Oh I'm 100% with you this is really annoying and I hope it gets fixed sooner than later
In the meantime, if you're changing your info.plist file a lot, you should have a look at the unity xcode api and post build processes, all the xcode settings are editable in code from inside Unity so you will never have to worry about this file again.
https://docs.unity3d.com/ScriptReference/iOS.Xcode.PlistDocument.html
There are some good examples on how to use this API to edit the plist file on these forums.

 

I have same issue.
I use Unity3D 2019.2.6f1 and Xcode 11.0 on OS Mojave 10.14.6
'usymtool' is always eat all ram when I build or archive app in Xcode and mac is no response.

 

I have meet the same problem, at Unity 2018.4.9, Xcode 11.1 . on OS S Mojave 10.14.6, I found the problem is after append xcode project, In Xcode Build Phases add a lot Process symbols step. each time append one, and finnally eat up all my ram, by delete these steps and left only one fix it. and next time append project check if there is duplicate Process symbols step. seem like a bug

 

This happened to me too and updating MacOS or xCode didn't work.
However deleting the build folder and using Build instead of Build And Run helps.

 

We are having this issue too.

 

Deng-Jia is correct. For anyone still having this problem (I know I was on 2018.4.12), go to Build Phases in XCode and delete all of the Process Symbols phases EXCEPT FOR ONE

 

The question of what usymtool is still needs to be answered. I can't find anything about it in the documentation.
Not running the script has no documented downside.

 

usymtool generates the project's symbol files

"The symbol files contains debug symbols which are used to debug on specific processor and iOS version and when some crash or error occurs, those symbols are used to create crash reports."

 

Where does it say that? Xcode generates the dSYMs based on the generated IL2CPP. What does usymtool do? If it was generating project symbol files useful out of Unity Cloud then it should have clear output and not fail the build when connecting to Unity Cloud doesn't succeed (see link at bottom).

Literally from https://www.tutorialspoint.com/what-is-processing-symbol-files-message-in-xcode where they are talking about iOS symbol files, not the project specific desymbolication files that you mention.

If usymtool generates the project's symbol files, where are the generated files?

I've also asked my question here https://forum.unity.com/threads/upl...stics-when-building-from-command-line.604780/

 

More specifically it generates symbols and uploads them to Crash Reporting.

Take a look at https://github.com/Unity-Technologi...itor/CrashReporting/Managed/CrashReporting.cs

The downsides to not using it look to be a logwarning and no crash reporting on their dashboard. So not including it in your build process might be okay if you don't need the crash reporting.

 

It looks like this issue is fixed in 2019.3: https://issuetracker.unity3d.com/is...equent-append-build-when-services-are-enabled

 

Thank you so much!!!

 

That works

 

Worked for me too thanks! Does anyone know if there's a way to automate this? I'm staying on 2018.LTS for my project and it would be nice to not have to worry about clearing this out all the time.

 

bump, Can i automate deleting duplicate tasks?

 

Worked for me. Thank you!

 

Thank you!!

 

I also want to know

Does anyone know how to stop him from appearing?

 

I had just encounter this issue last night. I bought a new laptop with 64 GB ram, and after building Xcode project for several times, my ram ran out. Then I found that there were multiple "usymtool" in the memory, searching "usymtool" brought me to this thread. Unity fixed it in 2019.3, but didn't back-port it to 2018.4. I am using 2018.4.22f1 by the way.

 

Hey guys, wth is this, this is taking 4gb ram, even after closing Unity Editor and Unity Hub it stays there!
I'm on Windows btw, Unity version 2019.4.12f1.

Edit: it vanished after a couple of minutes after I closed Editor/Hub.

 

I think the reason it stayed there after it was closed is because it hadn't finished uploading the symbols zip to Unity Cloud