Am Donnerstag, 19. Mai 2016 19:58:50 UTC+2 schrieb Tobias B. Besemer:
> Am Donnerstag, 19. Mai 2016 19:53:40 UTC+2 schrieb Tobias B. Besemer:
> > Am Donnerstag, 19. Mai 2016 17:46:58 UTC+2 schrieb Gijs Kruitbosch:
> > > On 19/05/2016 16:35, Tobias B. Besemer wrote:
> > > > Due to the upcoming requirement of SSE2 to run Firefox that is 
> > > > discussed here:
> > > > https://groups.google.com/forum/#!topic/mozilla.dev.platform/v0QAe2olnH0
> > > >
> > > > ...I had a look on...
> > > > Bug 1271755 - [meta] Require SSE2 to run Firefox
> > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1271755
> > > >
> > > > ...then on...
> > > > Bug 1270664 - Backout MSVC 2015 from aurora
> > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1270664
> > > >
> > > > ...and then the crash that comes up on non-SSE2-Systems...
> > > > Bug 1265615 - crash in SkPath::isRectContour
> > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1265615
> > > >
> > > > As I was interested in what kind of configurations that are, I opened:
> > > > https://crash-stats.mozilla.com/signature/?product=Firefox&signature=SkPath%3A%3AisRectContour
> > > >
> > > > ...here I get just 1 crash in the last 7 days with FF49.0a1 and 
> > > > "Process Type = content".
> > > >
> > > > So what is "Process Type = content" in "mozilla crash reports"?
> > > 
> > > It means that when using electrolysis/e10s/"process separation for web 
> > > content", the process running/displaying (ish) web content crashed 
> > > (rather than Firefox as a whole crashing). It has nothing to do with 
> > > SSE(2).
> > > 
> > > > And how I can have a look on the crash reports of e.g. the last ~30 
> > > > days?
> > > 
> > > There are too many for looking at all crash reports to be a meaningful 
> > > operation. If you mean all crash reports with that signature,
> > > 
> > > https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=28&signature=SkPath%3A%3AisRectContour
> > > 
> > > ~ Gijs
> > 
> > OK, my fault!
> > No native speaker and I read "processOR type"... ^^
> > Processor is that what I'm was looking for...
> > 
> > So I had a look at...
> > https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=28&signature=SkPath%3A%3AisRectContour
> > 
> > ...then "View ALL products and versions for this signature."...
> > https://crash-stats.mozilla.com/report/list?date=2016-05-19&range_unit=days&range_value=28&signature=SkPath%3A%3AisRectContour
> > 
> > ...and then had on this huge amount of two reports a look... ;-)
> > https://crash-stats.mozilla.com/report/list?date=2016-05-19&range_unit=days&range_value=28&signature=SkPath%3A%3AisRectContour#tab-reports
> > 
> > I see:
> > Build Architecture Info = AuthenticAMD family 6 model 4 stepping 2 | 1
> > Build Architecture Info = GenuineIntel family 6 model 15 stepping 13 | 2
> > 
> > ...what IMHO means that the user have just deactivated SSE2-Support in 
> > BIOS...
> 
> Question is:
> If Mozilla will really "Backout MSVC 2015 from aurora" because 2 people are 
> not able to configure there PCs right in BIOS ???
> https://bugzilla.mozilla.org/show_bug.cgi?id=1270664

OK, seems to be not 100% correct!

Build Architecture Info = AuthenticAMD family 6 model 4 stepping 2 | 1
Seems to be:
Athlon 1200 (Thunderbird)
AMD Name String: AMD Athlon(tm) Processor
Features: FPU TSC CX8 CMOV FXSR MMX
http://www.masmforum.com/board/index.php?PHPSESSID=8d46cd4ecb1688be429ab49694ec53e6&topic=1909.5;wap2
(I'm wonder that this system can run Win7!)

And...
Build Architecture Info = GenuineIntel family 6 model 15 stepping 13 | 2
Seems to be somethink like this:
Processor Intel(R) Xeon(R) CPU 5130 @ 2.00GHz @ 2.00 GHz
2 Processors, 4 Threads
Processor ID GenuineIntel Family 6 Model 15 Stepping 6
L1 Instruction Cache 32.0 KB x 2
L1 Data Cache 32.0 KB x 2
L2 Cache 4.00 MB
L3 Cache 0.00 B
Memory 3.86 GB
http://www1.hft-leipzig.de/s114122/geekbenchscore.html
(With WinXP.)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to