View Single Post
Posts: 74 | Thanked: 355 times | Joined on Aug 2017
#95
Originally Posted by TMavica View Post
memory killer is too often happen, so i made a swap memory, the problem is solved
No sure, if this is caused by the available RAM, as there are around 800 MB free on my device:
Code:
[root@Sailfish nemo]# free -m
             total       used       free     shared    buffers     cached
Mem:   2835       2059        776          0         52        682
-/+ buffers/cache:       1325       1510
Swap:            0          0          0
Nevertheless, adding swap is no big deal, and if it prevents unwanted closing of apps, let's do it. Below, I create a swapfile in /home which is the biggest partition available. Placing it directly in /home is somewhat unaesthetic, but we have to work with what's available. Putting it on the sdcard is a dumb idea because a) access speeds are way slower and b) it would wear the sdcard quite badly.

As always: DISCLAIMER: You're doing this on your own risk, I'm not responsible if something goes wrong. This reduces the available space for the user data by the amount of swap you are adding.

Please use the method provided by TMavica here as it does not requires parts of the user data partition: https://talk.maemo.org/showpost.php?...&postcount=111

below only for reference:
You can choose the size of the swap in the first comand (fallocate), either use M (for MB) or G (for GB). In my example, I create a 2 GB swap file.
Code:
# Create the swapfile
fallocate -l 2G /home/swapfile
# Set permissions
chmod 600 /home/swapfile
# Prepare file as swap
mkswap /home/swapfile
# Enable swap
swapon /home/swapfile

# Now, you can check that swap memory is available:
free -m

# Finally, add an entry to /etc/fstab so the swap gets enabled on boot
echo "/home/swapfile none swap defaults 0 0" >> /etc/fstab
If you want to remove the swap file any time (e.g. you need the space), delete the entry in /etc/fstab, disable it with
Code:
swapoff /home/swapfile
and delete the file.



Successfully updated from 2.1.3.7 to 2.1.4.13 on Oneplus 3T. So far: Jolla Together app is crashing on a regular basis when one starts scrolling.
Same for me. I'd suspect this is not a memory issue but maybe rather some incompatibility with the browser API!? It always crashes when you are in the middle of the loaded page (according to the scrollbar), so I'd suspect it tries to load more entries and fails.

Last edited by jenix; 2018-02-21 at 09:08. Reason: Refer to guide for zram swap, as it is more efficient
 

The Following 11 Users Say Thank You to jenix For This Useful Post: