Closed
Bug 543083
Opened 14 years ago
Closed 14 years ago
Gather emails for yslow crashes so we can contact users
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
1.5
People
(Reporter: morgamic, Assigned: ozten)
Details
Attachments
(2 files)
Austin, can we generate a query to gather all emails attached to the yslow crashes? Damon, can you provide the signature info we should be looking for?
Reporter | ||
Updated•14 years ago
|
Target Milestone: 0.6 → 1.5
Assignee | ||
Comment 1•14 years ago
|
||
If all the crashes have a uniq signature pattern... yep. As soon as Damon provides the signatures or group of signatures, we can make this happen. If we have to look at the modules list... not so much.
Comment 2•14 years ago
|
||
Signatures: nsXHREventTarget::GetParentObject(nsIScriptGlobalObject**) and: XPCWrappedNative::GetNewOrUsed(XPCCallContext&, nsISupports*, XPCWrappedNativeScope*, XPCNativeInterface*, nsWrapperCache*, int, XPCWrappedNative**) and: nsEventTargetSH::PreCreate(nsISupports*, JSContext*, JSObject*, JSObject**) Also, since more and more people are encountering this crash, we'll need to keep track of dates. For example, we'll pull everyone that crashed up until this morning. Notify them, then, we'll pull another week or so, and notify them. Also, who is going to write the script to actually send the email? I can provide the text of the mail to be sent.
Assignee | ||
Comment 3•14 years ago
|
||
Thanks! Should we use a generic service that takes CSV? (Marketing has a MailChimp account) What is the start date for this search?
Assignee | ||
Comment 4•14 years ago
|
||
'nsEventTargetSH::PreCreate(nsISupports*, JSContext*, JSObject*, JSObject**)' had no matches in realistic dev database. It's an out of date snapshot of prod (maybe 3 weeks out of date or less)
Comment 5•14 years ago
|
||
Yeah, we'll need something more recent, as up to date as possible, really. The spike occurred on 3.6 release.
Comment 6•14 years ago
|
||
And, I *hope* the recent data loss of 10 days does not include this info? **** if it does.
Assignee | ||
Comment 7•14 years ago
|
||
Assignee | ||
Comment 8•14 years ago
|
||
Assignee | ||
Comment 9•14 years ago
|
||
(In reply to comment #6) We should be fine. The 10 day window of crashes will be safe in the database*. * Except for the window of unprocessed crashes, which should be hours not days worth
Assignee | ||
Comment 10•14 years ago
|
||
(In reply to comment #5) I'll file an IT request to get the emails since 9/1/2009 in CSV format.
Assignee | ||
Comment 11•14 years ago
|
||
Is this bug still valid? I have the email addresses. Next steps or close invalid?
Comment 12•14 years ago
|
||
We should still send out the emails, so, I don't think this is invalid. Question is: What's the next step to sending out the emails? Where are they?
Assignee | ||
Comment 13•14 years ago
|
||
I have a csv file containing the emails. I can send this to you or ?. Thanks.
Assignee | ||
Comment 14•14 years ago
|
||
Sigh. I might not have this list after all. The file I'm thinking of is from 9/2009. The IT bug says that it was emailed to me. Please advice what the next step is and I'll ask again for the list.
Assignee | ||
Comment 15•14 years ago
|
||
Okay, Bug#543099 has the file.
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•