I would like to start off by saying that I am using the 2.1.1 version of WhatPulse, running on Windows 7 64bit.
What happened is, suddenly, my cursor becomes extremely slow – no longer moving fluidly, rather it is jumping around instead of moving continuously-- and every time I move the cursor around I get this strange beeping sound. After a short while, WhatPulse crashes and all the problems fade away. This is not the first time this has happened, it has happened to me before on a few occasions when using version 1.7 (I believe).
I have here some footage of what happened: Link. I was streaming some StarCraft II: Heart of the Swarm ladder matches, then bam, this event occurred but, like I said, as soon as WhatPulse crashed, everything went back to normal. The video ends before the error message saying that WhatPulse is no longer responding pops up but, I believe you get the point.
The programs I was running in the background while this was happening was as follows: Ventrilo, VLC media player, Open Broadcaster Software (32bit), Hot Virtual Keyboard, Google Chrome and, WhatPulse.
I can not seem to locate any crash log of this event. I hope this was helpful; if you need more information, I will try my best to provide it.
There are a few occasions where Windows can shut out the client, making it utterly confused and have it crash. This sometimes happens where the system is on a higher load than normal.
If there is anything logged, it will be in the %LOCALAPPDATA%\WhatPulse directory. Look for a client.log.
Is Client.log the name I should be looking for; I can’t find it. Perhaps I am not looking in the right place, the only files I can find is “Debug.log”, “Pulses.log”, and “app.log”
Since I can’t find a crash log, I have another question. Going back to what you said about Windows shutting out the client when the system is at a higher load, if I were to open up task manger, go into processes and, set whatpulse.exe’s priority to above normal, would that, perhaps, fix the issue I have?
(I’ll test it out and try to recreate the original crashes condition)
It might help if you set the process priority…but if it was a one time thing, I wouldn’t bother with it, as that’s something you need to set every time it’s restarted.
15-06-2013 12:25:43.369 INFO Starting WhatPulse...
15-06-2013 12:25:43.648 DEBUG Database file: "C:/Users/Quico/AppData/Local/WhatPulse/whatpulse.db"
15-06-2013 12:25:43.673 DEBUG Database check: "ok"
15-06-2013 12:25:43.674 DEBUG Opened database in: 26 ms
15-06-2013 12:25:43.678 DEBUG Running WhatPulse as Administrator! :-)
15-06-2013 12:25:43.678 DEBUG Encrypted file: "C:/Users/Quico/AppData/Local/WhatPulse/whatpulse.wpw"
15-06-2013 12:25:44.709 DEBUG Opening GeoIP database: "C:/Users/Quico/AppData/Local/WhatPulse/GeoIP.dat"
15-06-2013 12:25:44.798 DEBUG enableInputHook: true
15-06-2013 12:25:44.799 DEBUG LowLevelHookHandler starting
15-06-2013 12:25:44.799 DEBUG Enabling lowlevel input hooks
15-06-2013 12:25:44.799 DEBUG Starting PcapNetworkTrafficMonitor..
15-06-2013 12:25:44.805 DEBUG Found new interface: 19 "{62725DAB-0D10-4699-818B-7952192F4F94}" "4C:60:DE:88:3E:C4" "NETGEAR WNA3100 N300 Wireless USB"
15-06-2013 12:25:44.806 DEBUG PcapNetworkTrafficMonitor: Starting interface 19
15-06-2013 12:25:44.825 DEBUG pcap thread started on interface "\Device\NPF_{62725DAB-0D10-4699-818B-7952192F4F94}"
15-06-2013 12:25:44.846 DEBUG WhatPulse has started
15-06-2013 12:25:47.811 WARN QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
15-06-2013 12:30:20.019 DEBUG Detected system suspend!
15-06-2013 12:30:20.020 DEBUG Stopping PcapNetworkTrafficMonitor..
15-06-2013 12:30:20.020 DEBUG enableInputHook: false
15-06-2013 12:30:20.021 DEBUG LowLevelHookHandler stopping
15-06-2013 12:30:20.031 DEBUG Stopping PcapNetworkTrafficMonitor..
The thing is, I am about 90% sure it crashed on June 12th. So, all these stuff about the 15th, I have no idea. But, that was everything inside of the app.log. Again, if I need to provide more information just let me know and I will get right to it.
(Also, I haven’t yet had time to test the higher priority level. I will, however, test it tomorrow. It would be slightly unfortunate to have to set it every time but, if it works, it works.)
I can mention that this exact issue has happened for me twice now (over the course of a couple of months). The only application that I was using at the time was Google Chrome for surfing.