diff options
| author | stevenjb@google.com <stevenjb@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-16 23:54:10 +0000 |
|---|---|---|
| committer | stevenjb@google.com <stevenjb@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-16 23:54:10 +0000 |
| commit | 1a10a0ccf708a6453d515706390966605b9ce83a (patch) | |
| tree | 6372ba7423fe11853a457e0f97632d26badaab70 | |
| parent | 1ac01f930e63ed2c7216ab24cd8a6b318042d444 (diff) | |
| download | chromium_src-1a10a0ccf708a6453d515706390966605b9ce83a.zip chromium_src-1a10a0ccf708a6453d515706390966605b9ce83a.tar.gz chromium_src-1a10a0ccf708a6453d515706390966605b9ce83a.tar.bz2 | |
Initialize all values in BugReprotData.
On ToT I found that if I issued a bug report quickly it would crash because the syslogs data was not ready, presumably because fetching that data was put on a separate thread.
I'm trying to confirm that this is the same issue as the cras repport in chromium-os:15253, but regardless this simple fix should be in the M12 branch.
BUG=chromium-os:15253
TEST=Report an issue immediately after logging in. Chrome should not crash.
Review URL: http://codereview.chromium.org/7016045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85563 0039d316-1c4b-4281-b951-d872f2087c98
| -rw-r--r-- | chrome/browser/bug_report_data.cc | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/chrome/browser/bug_report_data.cc b/chrome/browser/bug_report_data.cc index e4d4866..6674570 100644 --- a/chrome/browser/bug_report_data.cc +++ b/chrome/browser/bug_report_data.cc @@ -12,7 +12,10 @@ BugReportData::BugReportData() : profile_(NULL), problem_type_(0) #if defined(OS_CHROMEOS) - , sent_report_(false), send_sys_info_(false) + , sys_info_(NULL) + , zip_content_(NULL) + , sent_report_(false) + , send_sys_info_(false) #endif { } |