Q: Computer do not hibernate when battery drained off

The report says Chrome is preventing it from sleeping. Quit Chrome.

By the way... hibernate is the same as sleep?

No.

Sleep keeps power to RAM so when you wake, so there is slight power drain while asleep.  But waking up a sleeping Mac is fast.

Hibernate, writes the contents of RAM to /private/var/vm/SleepImage, and then zero power is used.  When the Mac is started backup, you have to wait while RAM is repopulated from the SleepImage.  This is slower than a sleeping Mac (although if you have an SSD, it is not too slow).

A sleeping Mac will eventually drain the battery to zero.  By default, when a Mac goes to sleep, it also writes RAM to SleepImage, so if the battery does die while asleep, the Mac will then use the SleepImage.

A hibernating Mac can keep a charge for a very long time, as it is not using any power at all.  The battery will eventually loose power as any battery will if you leave it uncharged for a long enough period of time (months/years).

The computer do not hibernates when the battery is drained off. I think it is a configuration / software issue, because I recently erase de content of the disk and created a new user. In that configuration the computer performed the hibernation and the end of the battery.

Do you have any utilities such as SmartSleep, which will play with the Sleep and Hibernate settings dynamically?

Do you have system preferences -> energy saver -> battery -> computer sleep -> Never?

If not, then by default, the Mac should go to sleep when the battery gets to a minimum power level.  In going to sleep, it should create a SleepImage, so that if the battery dies when it is asleep it will still preserve the state of the Mac.

However, if the battery is dying suddenly before it reaches the threshold where the Mac would go to sleep, then the Mac will not have a chance to go to sleep and create a SleepImage.

Some batteries fail in such a way that they say they have nn%, then when they hit nn-1%, they die.  It is possible your Mac's battery is not degrading its charge in a predictable way, and the Mac does not know it should go to sleep.

It is also possible that you have an app running that is telling the Mac to not sleep.  This would NOT have anything to do with the pram settings you have been displaying, it would just be telling the operating system that it is busy doing something and thus the OS should not sleep just now.  I do not know if would stop the battery very low forced sleep or not.  I'm speculating on that.

My best guess is that your battery is not correctly reporting when it is about to run out of power.

PS/ When the computer have just 10 minutes of battery a banner appears warning me... then no more warnings, just switch off.

Looking a little more at your pmset values hibernatemode=3 is the standard default for a Mac laptop, so that mostly leaves software "maybe" interfering (and I really do not know that it could really interfere), and the battery and the OS not being clear on just when power is going to stop.

Hopefully battery recalibration will resolve the issue.

From "man pmset"

...

	hibernatemode = 3 (binary 0011) by default on supported portables. The
	system will store a copy of memory to persistent storage (the disk), and
	will power memory during sleep. The system will wake from memory, unless
	a power loss forces it to restore from disk image.

...

That last reference to "power loss forces" is talking about when you put your Mac to sleep and leave it sleeping so long that the "power memory during sleep" finally drains the battery to empty.  It does not refer to the situation you are experiencing where you Mac is not going to sleep before loosing power.

You might check the following.  Put your Mac to sleep.  Wake it backup.  Now use the Terminal and see if you have a sleepimage file:

ls -l /var/vm

-rw-------  1 root wheel   67108864 Nov  6 10:15 swapfile0

-rw-------  1 root wheel 1073741824 Nov  6 10:15 swapfile1

-rw------T  1 root wheel 8589934592 Nov 17 08:54 sleepimage

You should see one or more swapfile(s) and sleepimage.  If you do not see sleepimage, that might also indicate a problem creating the sleepimage, and since your battery is already nearly empty when the Mac tries to go to sleep, maybe it is not longer after, that it dies without a sleepimage to restore from.

NOTE: sleepimage is going going to be big.  The one above, from my Macbook Pro, is 8+ gigabytes.  It could be even larger as I have 16GB of RAM in my Macbook Pro.  So you need to have enough free storage on your Mac to create the sleepimage.

   pid 320(Google Chrome): [0x0000000100000165] 00:25:58 NoIdleSleepAssertion named: "WebRTC has active PeerConnections."

You may need to investigate "WebRTC has active PeerConnections" from your assertions report.  I did some Google searching and found several reports about sleep issues caused by some Chrome plug-ins.

Perhaps this is your root cause.

I am mostly just throwing ideas at the wall, and seeing what sticks.  While I was suggesting the battery is at fault, I would be very happy if it turned out to be software, as in my years of playing with computers, most times when you want to blame the hardware it turns out to be software (except for disk drives which always seem to die on me eventually ).

The only difference is, it asked me for my password, when normally it does not because I have the automatic login to my account enable.

If you have whole disk encryption via Mac OS X's FileVault, it will ask for the password in order to unlock the disk before a cold boot.

Or if you have the Mac set to ask for your password after going into the screen saver, it should ask for the password when restoring from a SleepImage (I think, as I rarely get into a situation where I've run my battery all the way down to zero - it has happened, but not enough for me to remember exactly what I saw).

Wiping your system is an option, however, I am unsure as to what it will do.  So for what "I think", it might be best to not trust my opinion on something as drastic as wiping and reinstalling

I am thinking to delete everything and install mavericks again.

Make sure you have a copy of Mavericks "BECAUSE" it is NO longer available from the App Store.  You can only get Yosemite.

AND NOT MATTER WHAT, make sure you have a backup (I am the paranoid type and make sure I have 2 working backups before I ever attempt wiping my boot disk).  I like SuperDuper and Carbon Copy Cloner for my backups whenever I do a system upgrade or disk replacement.  Wiping the system is like a disk replacement.  And test that the clones boot.

Then load everything from my backup except the system preferences.

The energy and hibernation rules come from the system preferences, not from the user preferences, right?

I am unsure where they are set.  And 'pmset' may exist in power management or PRAM

<OS X Mavericks: Reset your computer’s PRAM>

<Intel-based Macs: Resetting the System Management Controller (SMC) - Apple Support>

But if you do decide to install from scratch, why not run a test without restoring.  Run your test on a clean system, or install just enough to run your test.  Do not pulling any of your other stuff until the test is over. That way you know if it is part of the Mac hardware (PRAM and SMC on-chip settings are part of the hardware), or if it is software or software configuration files that are sitting on your backup.

Other option would be reinstall the system over the one I have here, but I do not really know if it could work. What do you think?

Still make sure you have a backup (again I'm paranoid and always have 2).

Installing over the existing system is less drastic than wiping and installing new.   I've heard of installing over the existing system being helpful for some, however, I cannot say from experience exactly what it does.  If you make good backups, it will most likely be the least drastic of the install ideas.