Closed Bug 630293 Opened 12 years ago Closed 5 years ago
Add crash URL .csv reports for Fennec
We publish text files with meta data for all the firefox crashes each day and these feed into a number of downstream testing and analysis systems. now that Fennec crash reporting is start to ramp up we need to start doing the same thing for that product. We can use the existing script with just one change for product name. output for the daily crash files can go to the same directory as firefox. for the output that contains confidential URL info put the output in cm-fs01://data/security_group/crash_urls/ chofmann@cm-fs01://data/security_group/crash_urls/Mobile-YYYYMMDD-crashdata.csv.gz for the URL stripped version put the output at people.mozilla.org://var/www/html/crash_analysis/"$day"/Mobile-YYYYMMDD=20110130-pub-crashdata.csv.gz These should be much smaller reports and should run pretty fast.
I'm not sure that Fennec actually reports a crash URL currently.
(In reply to comment #1) > I'm not sure that Fennec actually reports a crash URL currently. We should still be able to do the crash-stripped version though. Priority?
Actually, for the the stripped version, we are now just including the Fennec reports in the overall CSV file. As there's a product field in there anyhow and the Fennec volume is comparatively small, this works out well so far.
(In reply to Ted Mielczarek [:ted, :luser] from comment #1) > I'm not sure that Fennec actually reports a crash URL currently. We do. I can see the "URL" field containing data in Fennec 6 crash reports.
(In reply to Mark Finkle (:mfinkle) from comment #4) > (In reply to Ted Mielczarek [:ted, :luser] from comment #1) > > I'm not sure that Fennec actually reports a crash URL currently. > > We do. I can see the "URL" field containing data in Fennec 6 crash reports. Can you give me an example? I guess those are browser processes crashing and we don't get them for content processes crashing, right?
Note that I made that comment 7 months ago, so it's possible it has changed in the interim.
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #5) > (In reply to Mark Finkle (:mfinkle) from comment #4) > > (In reply to Ted Mielczarek [:ted, :luser] from comment #1) > > > I'm not sure that Fennec actually reports a crash URL currently. > > > > We do. I can see the "URL" field containing data in Fennec 6 crash reports. > > Can you give me an example? I guess those are browser processes crashing and > we don't get them for content processes crashing, right? https://crash-stats.mozilla.com/report/index/a2ba9551-4c59-4bfa-994a-7d8712110809 content crash with a URL
(In reply to Mark Finkle (:mfinkle) from comment #7) > content crash with a URL Nice, one thing less to worry about. :)
I'm only seeing about 50-100 urls per day out of 3000-3500 crash reports looking at a sample of a few days of data in .csv files. most times the url field shows \N for the last 12 days of July these are the top cxrashing urls 40774 Fennec \N 12 Fennec http://www.facebook.com/ 11 Fennec http://www.google.com/m?ie=UTF-8&oe=UTF-8&sourceid=navclient&gfns=1&q=firefox+video 9 Fennec about:home 6 Fennec http://xhamster.com/user/DBRAC 5 Fennec https://www.facebook.com/home.php 5 Fennec http://www.google.com/apps/intl/sv/business/index.html 5 Fennec http://www.dsebd.org/latest_share_price_scroll_l.php 5 Fennec http://touch.facebook.com/#!/home.php 5 Fennec http://m.facebook.com/?w2m&_rdr#!/home.php 4 Fennec http://www.maannews.net/arb/Default.aspx 4 Fennec http://www.dagbladet.no/ 4 Fennec http://www.briandils.com/blog/?p=65 4 Fennec http://touch.facebook.com/home.php 4 Fennec http://theomgmom.com/ 3 Fennec https://mozillademos.org/demos/dashboard-mobile/demo.html 3 Fennec http://www.wreckedexotics.com/newphotos/exotics2011jul25/2zayman_20110722_1.shtml 3 Fennec http://www.quibids.com/ 3 Fennec http://www.mangafox.com/ 3 Fennec http://www.google.com/apps/intl/en/business/index.html 3 Fennec http://www.google.com/ 3 Fennec http://www.facebook.com/home.php 3 Fennec http://www.facebook.com/?sk=ff&ap=1 3 Fennec http://www.betabeat.com/2011/07/29/why-my-mom-bought-an-android-returned-it-and-got-an-iphone/ 3 Fennec http://userscripts.org/scripts/review/103659 3 Fennec http://thechartpatterntrader.com/ 3 Fennec http://pet.kapook.com/view28324.html 3 Fennec http://news.nawaret.com/%d8%a7%d9%84%d8%b9%d8%a7%d9%84%d9%85-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a/%d8%a5%d8%b9%d9%84%d8%a7%d9%86-%d9%85%d9%81%d8%a7%d8%ac%d8%a6-%d8%b9%d9%86-%d9%85%d9%82%d8%aa%d9%84-%d8%b9%d8%a8%d8%af%d8%a7%d9%84%d9%81%d8%aa%d8%a7%d8%ad-%d 3 Fennec http://hespress.com/videos/34966.html 3 Fennec http://forum.kooora.com/f.aspx?mode=f&f=101 3 Fennec http://evanw.github.com/webgl-filter/ 3 Fennec http://dvd4arab.maktoob.com/ 3 Fennec http://articulo.mercadolibre.com.pe/MPE-16288393-thundercats-transformers-bmw-top-algodon-moda-retro-t-shirt-_JM 3 Fennec http://apps.facebook.com/vampiresgame/index.php?ref=bookmarks&count=0
looking closer it appears that all the urls are when the process type = content (makes sense), so I guess this tells us that +90% of the fennec crashes are in the firefox process. does that sound right?
No, we know that ~2/3 of all Fennec crashes are content crashes.
ah, ok. so I guess the landscape looks like this for those last 12 days of July 11194 Fennec \N --- firefox process 11192 Fennec \N \N --firefox process \N url 2 Fennec \N --firefox process blank url 30604 Fennec content -- content process 29582 Fennec content \N --content process \N url ~1000 Fennec content with url and a couple of blank urls
I was once crashing on http://evanw.github.com/webgl-filter/ on my LG Optimus Black once, I filed bug 677713 for it.
I filed bug 677727 on http://articulo.mercadolibre.com.pe/MPE-16288393-thundercats-transformers-bmw-top-algodon-moda-retro-t-shirt-_JM causing my Fennec on the LG Optimus Black to hang (but no crash at this point).
Component: Socorro → General
Product: Webtools → Socorro
if someone needs this still, use the crash-stats api
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.