OSX: Crash when pressing W and X at the same time

Jarl Arntzen 3 years ago updated by Tyler Owen (Lead Developer) 3 years ago 18

Here's the Problem Report for Lacuna Passage.txt

As I was walking (W) I accidentally pressed X. Immediate crash ensued.

Under review

X is the key to take photos. Can you confirm that you are able to take photos without crashing as long as you are not moving or pressing any other keys? Go to the photo app to make sure the photos are being taken.

It crashes consistently when pressing W + X. It can handle W + other buttons without a hitch. (A,S,D,F,R,Q,Z,C)

Here is the Player W-X.log. I was able to take some 4-5 photos while walking before it crashed.

Here is another log where I press X only Player - X only.log and still Lacuna Passage just crashes. I have not been able to take photos more than the first time and I did not check for their presence in the photo app.

I was able to press X with no crash Player - X success.log now but, alas, no pictures were to be found in the photo app. I could see a folder and 7 picture items inside but when I opened one of them, the picture was just a gray surface...


Okay, so both problems are definitely a memory issue similar to your crashes when entering and exiting the habitat. I'll be looking into this in conjunction with that related issue. I will be trying to measure the minimum ram memory needed for these actions and perhaps automatically adjusting the quality levels in a way that will prevent crashing. Thanks so much for your attached logs. They help a lot.

I edited your posts so that the log files are embedded directly here on the forum and aren't hosted on Dropbox in case you need to delete them. You should have the option to directly upload them yourself with the attachment button in the comment options. Thanks.

Thanks. I do not mind storing a few KB extra on my Dropbox, having paid for 1 TB. However, I can not seem to find an attachment button in the Userecho editor. 14 buttons in total + maximize but no attachment button.

Edit: Ohhhh....I can simply drag the files directly into the editor! Gonna do that from now on.

Huh, that's odd that you don't have a button but can still drag and drop. I have a button as an administrator and after doing some digging it seems like attachments are disabled by default for regular users. I guess if you can drag and drop that works, but I'll look into getting attachments officially enabled for all users.

Not sure I agree with the memory issue. I have 16 GB, using about 10GB when starting Lacuna 11GB when it completes loading. It never seems to go above that.

Weird, because I'm seeing "Could not allocate memory: System out of memory!" errors in all of your log files. I will have to get another set of eyes on these to see what is really going on here. You obviously have plenty of ram available.

Another crash. This time on Quality: Simple. Happened right at the start after enabling the scanner. The app does not appear to use more than 1.5 GB in the Activity Monitor, though. Plenty of RAM left. Problem Report for Lacuna Passage - 2.txt

Oh, hang on... I only just realised that it is possible to open the folder with the photos. I can see there are some 35 PNGs there. Som nicely rendered in very high quality, some gray and some black.

Yeah, I would assume that the gray/black ones were the ones that crashed the game when you tried to take them. Super weird that these would be showing up as memory errors when the game is using a fairly low share of memory. Thanks for the additional details.

Well. Not necessarily. I have maybe 5 gray in sequence, then a crash. Then 1 properly rendered --> Crash. Then 3 rendered --> Crash. Then 1 black, 1 gray, 1 rendered --> Crash. Seems to be no particular pattern here.

I'm just guessing that if I were able to take photos in the *current* quality (at least as an option), it would work.

Hmm, yeah that might be an interesting experiment. I'd really like to find the root cause of the memory errors though so I'll have to get back to you later once I've done some research on my end. Thanks again.


I'd like to find out if this issue has been impacted by the transition to 64 bit compatible builds on Mac that are included in the v0.51 update. Please let me know if you have a chance to test again. Thanks.

I can now confirm that this works beautifully on OSX