With the current linux client (2.4.1) I get a “Floating point exception” when starting the client. The only thing that helps is throwing all the local data away and starting from scratch.
This happened even when using the backup database and then resetting the token. In this case the program crashed immediately after the token reset and could not be started again.
This is happening every other program start (occured three times to me until now - had the computer running the whole week), but I haven’t really tried to reproduce this more often…
10-10-2014 10:40:42.609 INFO "Starting WhatPulse 2.4.1..."
10-10-2014 10:40:42.618 DEBUG Database file: "/home/****/.local/share/data/WhatPulse/whatpulse.db"
10-10-2014 10:40:42.628 DEBUG Database check: "ok"
10-10-2014 10:40:42.628 DEBUG Opened database in: 10 ms
10-10-2014 10:40:42.633 DEBUG Found proper permissions for network monitoring
10-10-2014 10:40:42.633 DEBUG Encrypted file: "/home/****/.local/share/data/WhatPulse/whatpulse.wpw"
10-10-2014 10:40:42.650 DEBUG Loaded application aliases
10-10-2014 10:40:42.816 DEBUG Opening GeoIP database: "/home/****/.local/share/data/WhatPulse/GeoIP.dat"
./whatpulse.sh: line 8: 3087 Floating point exception(core dumped) /home/****/Apps/whatpulse
OS is xubuntu 14.04
I’ve disabled per application and per country stats
I’ve now reproduced this problem a few times, even with windows.
There are two distinct moments this CAN happen:
Reboots / Shutting down the system. It seems that if the whatpulse program is closed by the operating system when the machine shuts down (or reboots), it might be caught in the wrong moment and writes a corrupt database to disk.
** Shutting down Whatpulse manually when shutting down the computer seems to help with this case in most cases
Auto-Pulsing - I’ve seen this happen at least five times now, twice on windows, three times on linux. It crashes immediately after an automatic pulse and then never recovers.
Since this problem still exists for me and happens quite often, I’ve found out, it happens randomly on pulsing. It doesn’t matter if it’s manual or automatic. The client immediately crashes and won’t recover until you delete the database files and start with a new configuration.
I’ve disabled all “per application statistics” and “per country statistics”
Windows Version is Win7 64bit in two cases.
Linux is xubuntu 14.10 in 3 cases and Debian 7 with XFCE in one case.