-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hard system crash on Solus #5
Comments
Hi, can you check with the new build? |
Please, Re open the issue, because it's real, I will close only when I don't see any problems with it anymore |
I'll give the new one a try! |
It definitely helped, it now gets to the point where it shows the Unity splash and no longer crashes the system. And I got a crash log this time:
|
I am going to guess this is the important bit:
That appears to be trying to allocate roughly 20 exabytes of ram. Looking around a bit it seems that a few other Unity projects have had similar errors, but I haven't yet found anywhere with a solution. Edit:
Here is the other example I found. They edited their question with a solution at the bottom. |
What is weird is, it is working just fine here, the error is with vulkan
for sure as you see, i will send you a version without initial window
resize and quality change, wait a bit.
Em qua, 3 de abr de 2019 16:57, Rujak Ironhammer <[email protected]>
escreveu:
… I am going to guess this is the important bit:
Could not allocate memory: System out of memory!
Trying to allocate: 18446744072657055745B with 16 alignment. MemoryLabel:
String
Allocation happened at: Line:314 in
./Runtime/Core/Containers/StringStorageDefault.h
Memory overview
That appears to be trying to allocate roughly 20 exabytes of ram. Looking
around a bit it seems that a few other Unity projects have had similar
errors, but I haven't yet found anywhere with a solution.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH2oRJwfTcnLyfAeibM1H0WyMpQufTVNks5vdQeygaJpZM4cWn4o>
.
|
Well, I'm doing a workaround that is not allowed by Hdrp, quality can't be changed the old way, hdrp assets can't be changed at runtime either, then even if is working and behaving as expected, I need to find another way. I'm doing this now. |
Thanks! I look forward to giving it a try! |
I tried several things then i found a unity employer explaining that I'm doing the only almost working way for now, then, I just need to refine it a little. Tomorrow I will send you a test version. |
Here it is, please test and thanks for your help. |
I gave it a go and it loads up the application and I can actually see the backgrounds this time but it still freezes up my X session. I have a slightly different log this time: A1: Run log.
I was able to switch to a different TTY due to it not entirely freezing this time and kill the process. From what I could tell it was still showing new frames in the application, just at a rate of one per every few minutes. Let me know if there is any more info I can give to help! P.S. Hopefully this setup for adding the log is a little more manageable. |
Thanks man |
Sorry for no updates, but i'm in my working days, i will continue when i come back home, in 6 days. |
Here is a Minimal Version, not so good graphics, please try, only trying to track the problem. Profiling
|
It was running a bit better so that I could get a screenshot this time. It was fluctuating between running at 60fps and 0fps. The actual memory use seemed to be just fine and CPU usage never showed anything unusual. Comparing it to the last build it visually looked the same when I ran each one. I am not entirely sure what it is normally supposed to look like but I thought I would mention. And no worries! I definitely want to give the software a try but I will definitely survive without it. Thank you so much for working with me on it! Terminal output
Player log
|
Thanks man, your help is really appreciated |
No problem at all! It seems that the new beta version of Unity might be the fix after all. I downloaded the most recent Unity Hub and the most recent beta build of Unity (2019.2.0a9) and figured out how to build it and it started working just fine. I don't know enough about Unity to tell if my distributions environment would change things but at least I can say it can work with the most recent pull from the HDRP branch! |
Thanks for all this amazing tests man!! |
I got this issue on Ubuntu 18.04 when I double clicked the window's top bar to enter widescreen (not full screen) mode. |
Can you try the 0.3.7 version and see if it works for all of you? |
Sorry it took quite so long to get back around to testing, but it is now starting up correctly on Solus using 0.3.7. I am able to import a diffuse map and generate the other maps correctly. Occasionally it is having similar issues to issue #13 but it no longer appears to have the memory issues that caused this issue! Other than that it is nice and snappy, all the options appear to work as intended, and exporting is working perfectly =D Thank you so much for working on it! I am happy to close out the issue whenever you are. |
I tried running the linux version on Solus and a few seconds after the window appears the entire system locks up. I am not sure exactly why this is happening due to Unity itself not having this issue. If you have any ideas for me to try to get it working I would be happy to help.
The text was updated successfully, but these errors were encountered: