Project Highrise

Project Highrise

View Stats:
Game crashes on startup - Ubuntu 20.04
So when I attempt to launch the game, the game starts for about a second or two and then immediately crashes afterwards. It does not produce a log file in the config folder for this game.

I'm running an I5-7500 with 8GB of ram, more then enough to run this game. I have also ran plenty of unity3d games on this computer before. And I am up to date on software. I'm running the recommended nvidia driver version 460.

In the meantime I'll run this on my other operating system until I can figure out a solution.

I've uploaded the strace file to google drive because pastebin does not allow none pro users to upload such huge files unfortunately.
https://drive.google.com/file/d/1iBCTd89AYtJCMHniik1g9Npj9AH9qjZO/view?usp=sharing
Last edited by Your Majesty Padded Gamer; Jun 27, 2021 @ 6:49pm
< >
Showing 1-15 of 16 comments
axios2006 Jun 27, 2021 @ 6:02pm 
Hi,

have you took a look at the pinned thread on this board?
Originally posted by axios2006:
Hi,

have you took a look at the pinned thread on this board?
Yes I have already looked at the pinned thread on this board, the force gl solutions did not help me I have tried the launch options already and they haven't resolved the issue. I also tried the language commend as well.
Last edited by Your Majesty Padded Gamer; Jun 27, 2021 @ 6:52pm
axios2006 Jun 27, 2021 @ 7:11pm 
Ok, Devs will look into this.
Stratus Jun 28, 2021 @ 4:33am 
The log shows your system is out of memory

write(1, "DynamicHeapAllocator allocation "..., 112DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 9223372036854775808. ) = 112 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=50000000}, NULL) = 0 write(1, "DynamicHeapAllocator allocation "..., 112DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 9223372036854775808. ) = 112 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=100000000}, NULL) = 0 write(1, "DynamicHeapAllocator allocation "..., 112DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 9223372036854775808. ) = 112 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=150000000}, NULL) = 0 write(1, "DynamicHeapAllocator allocation "..., 112DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 9223372036854775808. ) = 112 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=0, tv_nsec=200000000}, NULL) = 0 write(1, "DynamicHeapAllocator out of memo"..., 100DynamicHeapAllocator out of memory - Could not get memory for large allocation 9223372036854775808! ) = 100 write(1, "Could not allocate memory: Syste"..., 695Could not allocate memory: System out of memory! Trying to allocate: 9223372036854775808B with 16 alignment. MemoryLabel: NewDelete Allocation happend at: Line:0 in Overloaded New[] Memory overview [ ALLOC_DEFAULT ] used: 2570280B | peak: 0B | reserved: 8388608B [ ALLOC_TEMP_JOB ] used: 0B | peak: 0B | reserved: 1048576B [ ALLOC_TEMP_BACKGROUND_JOB ] used: 0B | peak: 0B | reserved: 1048576B [ ALLOC_GFX ] used: 0B | peak: 0B | reserved: 0B [ ALLOC_CACHEOBJECTS ] used: 86752B | peak: 0B | reserved: 8388608B [ ALLOC_TYPETREE ] used: 0B | peak: 0B | reserved: 0B [ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B [ ALLOC_TEMP_THREAD ] used: 32768B | peak: 0B | reserved: 1114112B ) = 695 write(1, "Could not allocate memory: Syste"..., 696Could not allocate memory: System out of memory! Trying to allocate: 9223372036854775808B with 16 alignment. MemoryLabel: NewDelete Allocation happend at: Line:0 in Overloaded New[]


After this the game throws an exception
write(1, "(Filename: Line: 1090)\n\n", 25(Filename: Line: 1090) ) = 25 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} --- write(1, "Receiving unhandled NULL excepti"..., 35Receiving unhandled NULL exception ) = 35
Stratus Jun 28, 2021 @ 4:40am 
have you tried running the Game.x86? In theory, the 32 bit version would try to allocate less memory
Originally posted by Stratus:
have you tried running the Game.x86? In theory, the 32 bit version would try to allocate less memory
The recommended RAM on the store page for this game is 4gb, I have literally twice that much at 8gb. I am able to run the windows version of this game at max graphics without any issue.

So I doubt that the issue is because I have not enough memory. But I'll try the 32 bit version and see if it runs.
Stratus Jun 28, 2021 @ 7:40am 
Originally posted by Your Majesty Padded Gamer:
Originally posted by Stratus:
have you tried running the Game.x86? In theory, the 32 bit version would try to allocate less memory
The recommended RAM on the store page for this game is 4gb, I have literally twice that much at 8gb. I am able to run the windows version of this game at max graphics without any issue.

So I doubt that the issue is because I have not enough memory. But I'll try the 32 bit version and see if it runs.

Its not a problem with your specific machine, you are correct. The issue is that the game is requesting more than the system has available. There have been related questions in the past where on some people's machines, the game is trying to allocate some absurd amount. The workaround has always been to use the 32bit version.

Personally, I haven't noticed a huge problem running the 32bit version, but I haven't ever made it to 80 stories either

Side note, I have bought all the expansions, I dont know if this has an impact or not
As would be expected really, I ran the 32 bit version and the same issue popped up. However I did run an strace for the 32 bit executable if that helps at all.

https://drive.google.com/file/d/18eCkDCRC5jO1heNMvJMpa4F2jzOOnN3t/view?usp=sharing
Stratus Jun 28, 2021 @ 8:11am 
You are correct, it is the same symptom although in this case its only trying to allocate 2.1gb

Can you tell me, are you running Ubuntu proper or one of the flavours (kubuntu, mate etc)?
Also you mention a driver version but what video card are you using?
Is this a fresh install or has it been upgraded from say 18.04?

I can try to reproduce this with a little more info. I can't say that I will get anywhere quickly but I might be able to find a work-around
Originally posted by Stratus:
You are correct, it is the same symptom although in this case its only trying to allocate 2.1gb

Can you tell me, are you running Ubuntu proper or one of the flavours (kubuntu, mate etc)?
Also you mention a driver version but what video card are you using?
Is this a fresh install or has it been upgraded from say 18.04?

I can try to reproduce this with a little more info. I can't say that I will get anywhere quickly but I might be able to find a work-around
It's a Nvidia geforce GTX 1060 6gb. It's a fresh install of 20.04.2 LTS. I am not using another flavor, just the standard Ubuntu.

If it helps my GNOME version is 3.36.8. My windowing system is X11.
Stratus Jun 28, 2021 @ 3:04pm 
While I dont have a 1060, I do have a 1050 lying around I should be able to get close. I'll see about finding a spare hdd in the next day or so to install Ubuntu 20.04 onto and see if i can reproduce this
Computerizer Jul 9, 2021 @ 2:52pm 
Hi, I'm also unable to run Project Highrise on Ubuntu 20.04. I've tried both the 32-bit and 64-bit versions and they both behave the same.

The 64-bit version tries to allocate 9,223,372 TB of memory:
Could not allocate memory: System out of memory! Trying to allocate: 9223372036854775808B with 16 alignment. MemoryLabel: NewDelete

The 32-bit version tries to allocate 2GB of memory:
Could not allocate memory: System out of memory! Trying to allocate: 2147483648B with 16 alignment. MemoryLabel: NewDelete Allocation happend at: Line:0 in Overloaded New[]

I have 16 GB of RAM on my machine.

$ ./Game.x86 Set current directory to /home/tyrel/.local/share/Steam/steamapps/common/Project Highrise Found path: /home/tyrel/.local/share/Steam/steamapps/common/Project Highrise/Game.x86 Mono path[0] = '/home/tyrel/.local/share/Steam/steamapps/common/Project Highrise/Game_Data/Managed' Mono config path = '/home/tyrel/.local/share/Steam/steamapps/common/Project Highrise/Game_Data/Mono/etc' Preloaded 'libCSteamworks.so' Preloaded 'libsteam_api.so' Unable to preload the following plugins: ScreenSelector.so ScreenSelector.so libCSteamworks.so libsteam_api.so DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 2147483648. DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 2147483648. DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 2147483648. DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 2147483648. DynamicHeapAllocator out of memory - Could not get memory for large allocation 2147483648! Could not allocate memory: System out of memory! Trying to allocate: 2147483648B with 16 alignment. MemoryLabel: NewDelete Allocation happend at: Line:0 in Overloaded New[]
stratl_00 Aug 2, 2021 @ 11:31pm 
Managed to get it working via running Steam with https://github.com/clearlinux/linux-steam-integration . Disclaimer: I'm using Manjaro though, so YMMV.
Last edited by stratl_00; Aug 2, 2021 @ 11:31pm
marciocr Sep 20, 2021 @ 5:54pm 
Originally posted by DissentialX:
Managed to get it working via running Steam with https://github.com/clearlinux/linux-steam-integration . Disclaimer: I'm using Manjaro though, so YMMV.

I had the same problem and the solution was the same.

The fix is in the Linux Steam Integration readme

Apply path based hotfixes to games

The redirect module contains some profiles to allow us to dynamically fix some issues that would otherwise require new builds of the games to see those issues resolved.

Project Highrise: Ensure we don't mmap a directory as a file (fixes invalid prefs path)
NReale3370 Dec 1, 2021 @ 1:11pm 
I've managed to solve the problem by using Gvim to edit in binary mode the Game.x86_64 file. I searched for every appearance of the words "prefs", there were 3. I changed them all to say "preds" instead, and now I have a prefs folder with prefs.txt and gameplay.txt in it and a preds file next to that folder that has the resolution information.
< >
Showing 1-15 of 16 comments
Per page: 1530 50