OOM doesn't necessarily kill the process you think it will. Read about it here:
http://lwn.net/Articles/317814/
I suspect what is happening is that because chrome uses a different process for each page, it's confusing the OOM-killer's heuristics and other processes are being killed rather than the parent chrome process.
According to this, the OOM-killer likes to kill niced processes. So try setting chrome to a niceness of greater than 0.. might make it more of a target :-)
This question is a bit old but I came across it while trying to mount an HFS+ partition in the same circumstances, and found the solution. I'm not quite sure how it is related to kernel version, mine is 3.13 (3.13.7-1 x86_64, Debian).
Short answer
Provide the size of the partition as well as its offset.
Long answer
First get the partition's information from Parted, in bytes; you need the Start and the Size numbers. Here is an example of Parted session (as you can guess, my hard drive image is /mnt/macbook.dd):
$ /sbin/parted /mnt/macbook.dd
WARNING: You are not superuser. Watch out for permissions.
GNU Parted 2.3
Using /mnt/macbook.dd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit
Unit? [compact]? b
(parted) p
Model: (file)
Disk /mnt/macbook.dd: 160041885696B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 20480B 209735679B 209715200B fat32 EFI system partition boot
2 209735680B 159907647487B 159697911808B hfs+ Customer
If I try to mount the partition by providing only the offset (start), I get the same error as you:
# mount -v -t hfsplus -o ro,loop,offset=209735680 /mnt/macbook.dd /media/mac
mount: enabling autoclear loopdev flag
mount: going to use the loop device /dev/loop0
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# dmesg | tail -n2
[117791.463123] hfsplus: invalid secondary volume header
[117791.463132] hfsplus: unable to find HFS+ superblock
By the way, you don't need to use losetup, mount does that for you automatically. Now if I add the partition's size (sizelimit), it works perfectly:
# mount -v -t hfsplus -o ro,loop,offset=209735680,sizelimit=159697911808 /mnt/macbook.dd /media/mac
mount: enabling autoclear loopdev flag
mount: going to use the loop device /dev/loop0
/mnt/macbook.dd on /media/mac type hfsplus (ro,offset=209735680,sizelimit=159697911808)
Best Answer
on later versions of linux kernels you are required to have a swap to hibernate. But there are work arounds. you can setup a swap file anywhere without partitioning.
Read about it here. https://www.kernel.org/doc/Documentation/power/swsusp-and-swap-files.txt
a quick solution (credit to Robert Munteanu)