WhatPulse Forums
2.1b2 crash on start - Printable Version

+- WhatPulse Forums (http://whatpulse.org/forums)
+-- Forum: Community (/forumdisplay.php?fid=34)
+--- Forum: Beta client (/forumdisplay.php?fid=74)
+---- Forum: Archive (/forumdisplay.php?fid=80)
+---- Thread: 2.1b2 crash on start (/showthread.php?tid=2810)

2.1b2 crash on start - Maverick - 03-27-2013 02:56 AM

Completely uninstalled all of Whatpulse before upgrading from 2.1b1 to 2.1b2. Running Whatpulse as Adminstrator on Windows 7 w/ the -verbose option shows this in the last few lines of app.log:
26-03-2013 21:34:28.775 TRACE Opening  ":/logo.png"
26-03-2013 21:34:28.804 TRACE WindowsSystem::getActiveApplicationPath()
26-03-2013 21:34:28.805 TRACE Opening  "Kernel32.dll"
26-03-2013 21:34:28.805 TRACE Opening  "."
26-03-2013 21:35:36.868  WARN QObject::killTimers: timers cannot be stopped from another thread

As well as the following pop-up message:
Microsoft Visual C++ Runtime Library

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.

RE: 2.1b2 crash on start - Bloopy - 04-02-2013 02:49 AM

Strange, I started getting the same errors in 2.1b1 on Windows XP. When I started the client again I ended up with two of whatpulse.exe in task manager. Then today it seemed to have frozen, so I killed it but I couldn't start it again. Eventually I installed 2.0.1 over the top of it and ran that, but it wanted me to login. So I installed 2.1b1 back, and it seems to be ok for now. Keys/clicks weren't lost.

RE: 2.1b2 crash on start - smitmartijn - 04-06-2013 07:49 PM

Luckily, I think I have found the issue. If the database (%LOCALAPPDATA%\WhatPulse\whatpulse.db) is corrupted somehow, it's supposed to load the whatpulse.db.backup file, but basically, it wasn't. It wasn't stopping altogether when the database is corrupted either, which meant it was throwing update queries to a corrupt database...do that enough times and the application will crash horribly. (the "WhatPulse has stopped in an unusual way" error)

That has just been fixed, so this should not happen anymore after 2.1b3 (probably tomorrow).