TroubleShootCrashOnStartup
Contents |
Symptom: Crash every time you launch WeSay
Is there a problem with your installation or computer?
Does it crash with just this one project? To test that, try opening the included sample data project, or run the configuration program, create a new project, and open it. If every project leads to a crash, you have some kind of install or operating system issue, which we don't have any experience with yet.
Is there a problem with the cache?
The cache is disposable. If it gets messed up, you can remove it, and WeSay will rebuild it on the next run.
1) Go to your project directory (e.g. My Documents\WeSay\<project name>)
2) rename the folder "cache" to "badcache"
3) run WeSay. It will rebuild the cache.
4) If all is well now, please zip and email your project directory to issues@wesay.org. Then delete "badcache".
You get a message about WeSay not saving some work from a previous session
If WeSay were to crash just right, it may leave an invalid "update" file around. The next time you run WeSay, it will notice this and give you a message. When it does this, it appends ".bad" to the offending file.
- Look in your project directory (e.g. My Documents\WeSay\<project name>) for anything ending in ".update.bad"
- You can open this the ".update.bad" file in a text editor (e.g. NotePad) to get an idea of what didn't get saved. Don't be surprise if it is empty. You may also zip and email it file to issues@wesay.org.
- There can be more than one messed up .update file, in which case you may get this message multiple times.
Is there a problem with an xml update file?
(this scenario may be impossible to reach now)
- Look in your project directory (e.g. My Documents\WeSay\<project name>) for anything ending in ".update"
- if there is something, perhaps it has some bad data. Rename it to ".badupdate"
- run WeSay
- If all is well now, please zip and email My Document\WeSay\<project name> to issues at wesay org.
