Confirm, emeritus
3,599
edits
Changes
no edit summary
** malware or other software causing crashes
** improperly installed software putting DLLs in our appdir
** bugs in our code (Cairo, other areas; using valgrind and purify Purify to find these)
* need to make sure that when we file a bug, it's got an owner who will drive towards a solution (gather data, find someone to help with analysis, figure out where the problem is, shepherd in a fix, see the bug closed)
* most crashes are in Windows, so if you need help in figuring out what's the best way to set up a Windows VM, ask
* would be good to have processing categorize crash signatures along the lines shaver posited above
** somehow mark signatures as "malware" or "external software" or more importantly "totally our code, nothing else loaded"
* jonas was concerned that we were assuming too much about the cause of crashes, but was convinced that there's no harm to it as long as we continue the Purify and Valgrind investigations
* dolske wondered if we should be broadcasting the "what caused the crash" piece to users
* should we spend time telling users that Safe Mode might fix their problem?
** beltzner felt that we could, but ultimately it's not as satisfying as either the Chrome solution (a crash doesn't take down the entire browser) or having the problem fixed on our side
