Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I need to report an intermittent crash of Google Chrome (stable channel) that I experience several times a week. However I strictly don't to share with Google some pieces of my user profile (certain cookies, site data and pieces of cache, some parts of my browsing history and the similar stuff). History is not synced with my Google Account.

I can live with losing several hours (or days) or browsing history and saved passwords (created while I am reproduce a crash), but it's absolutely necessary to maintain an up-to-date session (open tabs and windows), as it always reflects my current 'state of work' on multiple projects. During those hours/days, I won't be visiting the sites that I don't want to share info about.

My first idea is to create a replica of my user profile for the purposes of reproducing, clear up all sensitive info from it (or even populate a blank profile with only "{Last|Current} {Session|Tabs}" from my original profile). Then live with it until I report enough crashes, and after that copy the latest "{Last|Current} {Session|Tabs}" files from the replica to my original profile. Will such open tabs data from the temporary profile work with my original profile when moved back to it from temporary profile?

Alternatively I am considering to manually collect raw crash data with windbg. Will the log by windbg be human readable enough to make sure that it contains nothing I don't want to send to Google?

Any other ideas are appreciated.

share|improve this question
1  
Google already knows pretty much everything about you, including browsing history, etc. Don't fret about a crash report. –  Chipperyman Dec 15 '13 at 22:28
    
@chipperyman573 Not relevant to my question. –  yurkennis Dec 15 '13 at 22:31
1  
Its really simply. Create a backup of your profile data. At this point disable all syncing. Get your session to the point where you want it, submit the data you want to submit, then restore the backup profile. –  Ramhound Dec 16 '13 at 0:43
    
@ramhound Looks a valid answer in itself, why not post it as a real answer? Only need to keep latest session files (tabs and windows). –  yurkennis Dec 16 '13 at 4:18
1  
But you would still be in the same position: trying to sanitize sensitive data from the profile files before submitting anything. –  Synetech Dec 16 '13 at 18:35

1 Answer 1

how to report a crash to Google Chrome if I don't want to share certain pieces of my profile?

Instead of going through the built-in bug-reporting mechanism, try filing a bug report instead, and then let them tell you what they want or need. You may find out that they don’t need your files at all.

I can live with losing several hours (or days) or browsing history and saved passwords (created while I am reproduce a crash), but it's absolutely necessary to maintain an up-to-date session (open tabs and windows), as it always reflects my current 'state of work' on multiple projects. During those hours/days, I won't be visiting the sites that I don't want to share info about.

Then use a proper session-management extension like Session Buddy. That way, you can control every aspect of your session, including removing items from a saved session.

My first idea is to create a replica of my user profile for the purposes of reproducing, clear up all sensitive info from it (or even populate a blank profile with only "{Last|Current} {Session|Tabs}" from my original profile). Then live with it until I report enough crashes, and after that copy the latest "{Last|Current} {Session|Tabs}" files from the replica to my original profile. Will such open tabs data from the temporary profile work with my original profile when moved back to it from temporary profile?

Those files have no bearing on the profile itself and only include a list of the open tabs and windows, and the contents of the web forms you have open. Chrome will be able to use any session/tab files, including those from a different profile (at least from the same version).

Alternatively I am considering to manually collect raw crash data with windbg. Will the log by windbg be human readable enough to make sure that it contains nothing I don't want to send to Google?

You can use a program like Strings to examine the text contained in the crash dump (this particular one can extract both ASCII and Unicode text).

You can also use Nirsoft’s BlueScreenView to examine the decoded contents of the crash dump files. You’ll need to either save the dump to the default mini-dump folder (%SystemRoot%\MiniDump), or else tell BlueScreenView where to find your Chrome dumps in the advanced options (Ctrl+O):

Screenshot of BlueScreenView’s advanced options with dummy paths set

share|improve this answer
    
1. "try filing a bug report instead, and then let them tell you what they want or need": from my experience, I will be immediately directed to chromium.org/for-testers/bug-reporting-guidelines/… or a similar page. Hard to believe devs won't need a crash report. –  yurkennis Dec 16 '13 at 7:05
    
2. "Then use a proper session-management extension like Session Buddy. That way, you can control every aspect of your session, including removing items from a saved session." Don't see how this extension can help in my scenario. Exporting session from a crash-reporting profile to a CSV and importing it back into stable profile seem to result in loosing much data, like browsing history in individual tabs, pages that resulted from post requests etc. –  yurkennis Dec 16 '13 at 7:09
    
@yurkennis, it depends on the crash. It may be something they are aware of, in which case they may not need anything. Besides, that page asks for a crash dump which is surprisingly less likely to contain sensitive data than profile files. –  Synetech Dec 16 '13 at 7:09
    
3. "Chrome will be able to use any session/tab files, including those from a different profile (at least from the same version)." That's helpful, thanks. –  yurkennis Dec 16 '13 at 7:10
    
2.1. "which is surprisingly less likely to contain sensitive data than profile files" Of course I wasn't going to share profile files until asked for explicitly; my key concern at this stage is about sharing sensitive pieces in the crash log itself (either the manual one or the one Chrome sents automatically). –  yurkennis Dec 16 '13 at 7:12

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.