Re: Updating 32-bit Windows users to 64-bit Windows builds?

Am Freitag, 13. Mai 2016 10:34:59 UTC+2 schrieb bo...@mozilla.com: > On Thursday, 12 May 2016 21:36:53 UTC+1, Chris Peterson wrote: > > Yes. Flash and Silverlight both have 64-bit plugins that work in 64-bit > > Firefox. Streaming video services will likely move their Firefox users > > from

Re: What is "Process Type = content" in "mozilla crash reports"?

Am Donnerstag, 19. Mai 2016 23:03:16 UTC+2 schrieb Tobias B. Besemer: > Am Donnerstag, 19. Mai 2016 22:59:35 UTC+2 schrieb Tobias B. Besemer: > > Am Donnerstag, 19. Mai 2016 22:00:55 UTC+2 schrieb Nathan Froyd: > > > On Thu, May 19, 2016 at 1:58 PM, Tobias B. Besemer wrote: > > > > Question is: >

Re: What is "Process Type = content" in "mozilla crash reports"?

Am Donnerstag, 19. Mai 2016 23:25:15 UTC+2 schrieb Tobias B. Besemer: > Am Donnerstag, 19. Mai 2016 23:03:16 UTC+2 schrieb Tobias B. Besemer: > > Am Donnerstag, 19. Mai 2016 22:59:35 UTC+2 schrieb Tobias B. Besemer: > > > Am Donnerstag, 19. Mai 2016 22:00:55 UTC+2 schrieb Nathan Froyd: > > > > On

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

Closing out this thread - we made Linux 64 Debug builds Tier 1 mid-April, and last week we turned off the related buildbot jobs. All Linux 64 Debug builds and tests now happen exclusively in TaskCluster! Thank you all the teams and individuals that contributed to getting this done! We NI'd quite

Re: What is "Process Type = content" in "mozilla crash reports"?

Am Donnerstag, 19. Mai 2016 22:00:55 UTC+2 schrieb Nathan Froyd: > On Thu, May 19, 2016 at 1:58 PM, Tobias B. Besemer wrote: > > Question is: > > If Mozilla will really "Backout MSVC 2015 from aurora" because 2 people are > > not able to configure there PCs right in BIOS ??? > >

Re: Updating 32-bit Windows users to 64-bit Windows builds?

Am Donnerstag, 12. Mai 2016 18:22:53 UTC+2 schrieb David Baron: > On Thursday 2016-05-12 11:45 -0400, Ted Mielczarek wrote: > > requirement for x86-64 processors, and the overall performance should > > generally be better (modulo memory usage, I'm not sure if we have an > > exact comparison).

pushPrefEnv/popPrefEnv/flushPrefEnv now return Promises

Hello, One of the reasons developers have been avoiding pushPrefEnv compared to the synchronous set*Pref (with a registerCleanupFunction) is because pushPrefEnv required using a callback function to wait for the preference change before moving on in the test file. This can make the test flow

Re: Updating 32-bit Windows users to 64-bit Windows builds?

Am Donnerstag, 12. Mai 2016 18:56:19 UTC+2 schrieb Ben Hearsum: > Do you have thoughts on how we'll be able to serve the users the correct > build if we have to base the decision on plugins they may have or other > information that's not in the update ping? We can already detect 32-bit > builds

Re: pushPrefEnv/popPrefEnv/flushPrefEnv now return Promises

On Thu, May 19, 2016 at 4:09 PM, Matthew N. wrote: > As a reminder, the nice thing about pushPrefEnv is that the pref changes > are reverted at the end of the test file which avoids them leaking into > other tests unintentionally. > Another good thing about it is that

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Thu, May 19, 2016 at 4:24 PM, Xidorn Quan wrote: > On Fri, May 20, 2016 at 8:16 AM, Selena Deckelmann > wrote: > > > Closing out this thread - we made Linux 64 Debug builds Tier 1 mid-April, > > and last week we turned off the related buildbot jobs.

On the merits of bringing back MSVC2015 to 48 to fix a top crasher

Hi All, Tl;dr; The necko team has for months been chasing a windows only top crasher. It is a shutdown hang - Bug 1158189. The crash stopped happening on nightly-48 back in March and that ‘fixed state’ has been riding the normal trains. Last weekend it returned to crashing on aurora-48 but not on

Re: What is "Process Type = content" in "mozilla crash reports"?

Am Donnerstag, 19. Mai 2016 22:59:35 UTC+2 schrieb Tobias B. Besemer: > Am Donnerstag, 19. Mai 2016 22:00:55 UTC+2 schrieb Nathan Froyd: > > On Thu, May 19, 2016 at 1:58 PM, Tobias B. Besemer wrote: > > > Question is: > > > If Mozilla will really "Backout MSVC 2015 from aurora" because 2 people >

Re: Updating 32-bit Windows users to 64-bit Windows builds?

Am Freitag, 13. Mai 2016 14:35:52 UTC+2 schrieb Ben Hearsum: > On 2016-05-12 06:44 PM, khagar...@gmail.com wrote: > > On Thursday, May 12, 2016 at 11:47:15 PM UTC+2, Karl Tomlinson wrote: > >> Lawrence Mandel writes: > >> > >>> Do we need this criteria? > >>> > >>> RAM - Does it hurt to move an

Re: Updating 32-bit Windows users to 64-bit Windows builds?

Am Freitag, 13. Mai 2016 22:41:01 UTC+2 schrieb Benjamin Smedberg: > We have considered this, but in the grand rollout plans for 64-bit Firefox > it's low on the list. We're still dealing with Flash sandboxing/functional > regressions as a blocker for wider rollout, and the next step is probably >

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Fri, May 20, 2016 at 8:16 AM, Selena Deckelmann wrote: > Closing out this thread - we made Linux 64 Debug builds Tier 1 mid-April, > and last week we turned off the related buildbot jobs. > > All Linux 64 Debug builds and tests now happen exclusively in TaskCluster! > >

Re: IPCStream landed in mozilla-central

On Fri, May 20, 2016 at 2:19 AM, Ben Kelly wrote: > On Thu, May 19, 2016 at 1:41 PM, Andrew McCreight > wrote: > > > On Thu, May 19, 2016 at 8:04 AM, Ben Kelly wrote: > > > > > 3) Supports async pipe streams using a new

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Fri, May 20, 2016 at 9:36 AM, Gregory Szorc wrote: > On Thu, May 19, 2016 at 4:24 PM, Xidorn Quan > wrote: > >> On Fri, May 20, 2016 at 8:16 AM, Selena Deckelmann >> wrote: >> >> > Closing out this thread - we made Linux 64 Debug

Re: Updating 32-bit Windows users to 64-bit Windows builds?

On Thu, May 19, 2016 at 3:18 PM, Tobias B. Besemer < tobias.bese...@googlemail.com> wrote: > Am Freitag, 13. Mai 2016 22:41:01 UTC+2 schrieb Benjamin Smedberg: > > We have considered this, but in the grand rollout plans for 64-bit > Firefox > > it's low on the list. We're still dealing with Flash

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Fri, May 20, 2016 at 10:20 AM, J. Ryan Stinnett wrote: > On Thu, May 19, 2016 at 6:24 PM, Xidorn Quan > wrote: > > 2. I cannot retrigger any TC task. > > > > This is pretty annoying when I was debugging intermittent issues. > Hopefully > > they could

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Thu, May 19, 2016 at 07:20:30PM -0500, J. Ryan Stinnett wrote: > On Thu, May 19, 2016 at 6:24 PM, Xidorn Quan wrote: > > 2. I cannot retrigger any TC task. > > > > This is pretty annoying when I was debugging intermittent issues. Hopefully > > they could get fix before

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Thu, May 19, 2016 at 6:24 PM, Xidorn Quan wrote: > 2. I cannot retrigger any TC task. > > This is pretty annoying when I was debugging intermittent issues. Hopefully > they could get fix before we migrate all Linux builds to TaskCluster, > otherwise we will lose the

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Fri, May 20, 2016 at 8:16 AM, Selena Deckelmann wrote: > Closing out this thread - we made Linux 64 Debug builds Tier 1 mid-April, > and last week we turned off the related buildbot jobs. > > All Linux 64 Debug builds and tests now happen exclusively in TaskCluster! > >

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

Retriggering was unintentionally broke earlier this week. We will be making it a priority to fix this. I'm sorry that it has caused a great deal of frustration and soon we'll have it back! -Greg > On May 19, 2016, at 7:21 PM, J. Ryan Stinnett wrote: > >> On Thu, May 19, 2016

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

Could the lack of failure emails be specific to taskcluster jobs? https://treeherder.mozilla.org/#/jobs?repo=try=a8c6ab15dd8f ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Requiring SSE2 on all 32-bit x86 OSs

On Thu, May 19, 2016 at 12:07:42PM +0300, Henri Sivonen wrote: > On Wed, May 18, 2016 at 8:32 PM, Benjamin Smedberg > wrote: > > Can we require SSE2 for Mozilla builds of Firefox for Linux? Yes, I am > > comfortable making that decision today. > > Thank you! I filed >

Re: Requiring SSE2 on all 32-bit x86 OSs

On Thu, May 19, 2016 at 12:31 PM, Mike Hommey wrote: > I don't think anyone suggested to add support for runtime selection of > SSE2 for code that is not inline asm. The code that I'm most immediately interested in replacing with Rust with SSE2 intrinsics without runtime

Re: Requiring SSE2 on all 32-bit x86 OSs

On Wed, May 18, 2016 at 8:32 PM, Benjamin Smedberg wrote: > Can we require SSE2 for Mozilla builds of Firefox for Linux? Yes, I am > comfortable making that decision today. Thank you! I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1274196 for this. > Should we also

Re: Requiring SSE2 on all 32-bit x86 OSs (was: Re: Reverting to VS2013 on central and aurora)

On 2016-05-18 10:10, Henri Sivonen wrote: What do we need to do to reach a decision that it's indeed OK to treat *run-time* selection of SSE2 vs. non-SSE2 especially in Rust code as a "patches not even welcome" kind of thing, considering that this may lead to Linux distros shipping an 32-bit x86

Re: Requiring SSE2 on all 32-bit x86 OSs (was: Re: Reverting to VS2013 on central and aurora)

On Thu, May 19, 2016 at 12:30 PM, Kurt Roeckx wrote: > On 2016-05-18 10:10, Henri Sivonen wrote: >> >> What do we need to do to reach a decision that it's indeed OK to treat >> *run-time* selection of SSE2 vs. non-SSE2 especially in Rust code as a >> "patches not even welcome"

IPCStream landed in mozilla-central

Hi all, FYI, I've landed a new IPDL type in bug 1093357 called IPCStream. This is intended to make it easier to serialize nsIInputStreams across IPC. In short, IPCStream: 1) Supports our existing serializable nsInputStreams. 2) Also automatically handles send file descriptors using the

Re: Request Feedback - Submitting Canvas Frames, WebVR Compositor

This looks good to me in general -- for Gecko, this combined with offscreen canvas and canvas/webgl in workers is going to be the best way to get performant WebGL-based VR. This is likely going to be the better way to solve the custom-vsync for VR issue; while the large patch queue that I have

What is "Process Type = content" in "mozilla crash reports"?

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

Suggestion: Class or API to check pre-requirements of Firefox

As I'm lazy, plz read here: https://bugzilla.mozilla.org/show_bug.cgi?id=1271762 ;-) (It's really not much to read in the bug!) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: What is "Process Type = content" in "mozilla crash reports"?

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

Re: What is "Process Type = content" in "mozilla crash reports"?

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

Re: IPCStream landed in mozilla-central

On Thu, May 19, 2016 at 8:04 AM, Ben Kelly wrote: > 3) Supports async pipe streams using a new PSendStream actor from > *child-to-parent*. I have plans to add support for parent-to-child, but I > don't have a consumer yet and we need to figure out some issues with >

Re: Requiring SSE2 on all 32-bit x86 OSs (was: Re: Reverting to VS2013 on central and aurora)

On Thu, May 19, 2016 at 2:59 AM, Emanuel Hoogeveen < emanuel.hoogev...@gmail.com> wrote: > They do get the baseline compiler, which can still be significantly faster > than the interpreter, but Ion requires SSE2. Since the runtime detection > does just turn Ion off altogether, I don't know if we

Re: IPCStream landed in mozilla-central

On Thu, May 19, 2016 at 1:41 PM, Andrew McCreight wrote: > On Thu, May 19, 2016 at 8:04 AM, Ben Kelly wrote: > > > 3) Supports async pipe streams using a new PSendStream actor from > > *child-to-parent*. I have plans to add support for

Re: Intent to unship: HTML microdata API

On 5/19/16 2:08 PM, Emma Humphries wrote: Should I remove the component from Bugzilla and mark remaining bugs incomplete? Emma, Which component do you mean? But I suspect the answer is "no"... -Boris ___ dev-platform mailing list

Re: What is "Process Type = content" in "mozilla crash reports"?

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

Re: What is "Process Type = content" in "mozilla crash reports"?

Am Donnerstag, 19. Mai 2016 20:49:08 UTC+2 schrieb Tobias B. Besemer: > 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: > > > >

Intent to unship: HTML microdata API

Summary: The HTML Microdata API was removed from the spec due to lack of implementor interest. See . Our implementation of it breaks some pages (due to the itemId attributes it adds) and is a bunch of code. I would like to remove it.

Re: What is "Process Type = content" in "mozilla crash reports"?

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: > > >

Re: Intent to unship: HTML microdata API

> On May 19, 2016, at 10:55 AM, Boris Zbarsky wrote: > > Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=909633 > > Target release: 49 > > I believe I've removed all our in-browser dependencies on this stuff. I > haven't really checked addons because

Re: IPCStream landed in mozilla-central

On Thu, May 19, 2016 at 1:41 PM, Andrew McCreight wrote: > On Thu, May 19, 2016 at 8:04 AM, Ben Kelly wrote: > > > 3) Supports async pipe streams using a new PSendStream actor from > > *child-to-parent*. I have plans to add support for

Re: What is "Process Type = content" in "mozilla crash reports"?

On Thu, May 19, 2016 at 1:58 PM, Tobias B. Besemer wrote: > 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

Re: What is "Process Type = content" in "mozilla crash reports"?

Example for "GenuineIntel Family 6 Model 15 Stepping 13": http://browser.primatelabs.com/geekbench3/125284 (Intel Core 2 Duo T5800 @ 2.00 GHz) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform