mozilla.dev.platform Google Group

[RFC] Modules for workers

dtel...@mozilla.com (David Rajchenbach-Teller) — Sat, 18 May 2013 10:09:39 UT

Hi everyone,

As part of the ongoing effort to make (Chrome) Workers useful for
platform refactorings, we have been working on a lightweight module
loader for workers (bug 872421). This loader implements a minimal
version of CommonJS modules, aka require.js.

Example:

// Setup the loader. We need this once per worker.

Running Windows 7 & XP jobs on ix hardware

arme...@mozilla.com (Armen Zambrano G.) — Fri, 17 May 2013 20:07:52 UT

Hi all,
As of today, we run in parallel Windows 7 and Windows XP on iX hardware
as well as on minis.

Current status:
* Windows 7 on iX is running *visible* on FF23 based trees
* Windows XP on iX is running *hidden* on m-i, try and cedar

Sometime after Tuesday, I will:
* Evaluate and propose a date for Win7 on iX to take over rev3 minis

Re: Deferred display of XUL panel containing embedded iframe

matt...@salsitasoft.com (Matthew Gertner) — Fri, 17 May 2013 15:59:32 UT

For the record two people emailed me separately to suggest panel.style.visibility = 'hidden'. This works fine. The only caveat is that I still see the panel's old content for a split second if I make it visible again in the 'DOMContentLoaded' handler. If I wait for readystate to change to 'complete' then it works fine and I see the new content with no blinking. I'm not sure if this is because rendering has not necessarily finished when readystate is 'interactive' or if it's just coincidence (since 'complete' happens later).

Re: new build-time defines for controlling when features ship

ga...@gavinsharp.com (Gavin Sharp) — Fri, 17 May 2013 15:36:07 UT

[redirecting this to dev-platform only]

As mentioned in the firefox-dev thread, I don't expect this to be a serious
problem in practice, and I don't think preference flipping is sufficient to
cover all the use cases (some things can't be easily/cleanly
pref-controlled). If I'm wrong about that we can revisit automated

Re: new build-time defines for controlling when features ship

benja...@smedbergs.us (Benjamin Smedberg) — Fri, 17 May 2013 15:29:42 UT

My understanding of this is that we were going to limit use of all of
these options to control preference-flipping. In particular I'm worried
about build bustage that is only discovered at channel-uplift time.

As I remember our discussion about this, use of this flag needs explicit
approval from release drivers, and it should not be used as general

Re: Deferred display of XUL panel containing embedded iframe

nipino...@gmail.com — Fri, 17 May 2013 11:06:51 UT

Re: Deferred display of XUL panel containing embedded iframe

matt...@salsitasoft.com (Matthew Gertner) — Fri, 17 May 2013 08:40:12 UT

Is there another way to make the panel invisible without destroying the nsIFrame?

I can't see how to open the popup after the content is loaded since as far as I can see the iframe doesn't have a docshell until the popup is first opened.

Linux builds now using gcc 4.7 [Was: Re: Upcoming changes to the Linux 32-bits and Android builders]

m...@glandium.org (Mike Hommey) — Fri, 17 May 2013 06:37:34 UT

This turned out to be caused by bug 817700, which was backed out because
the same was happening on PGO builds with gcc 4.5. So everything is in
order to switch Linux builds to gcc 4.7, which I just landed on inbound.

Mike

Re: Forcing alphabetical order in moz.build files

g...@mozilla.com (Gregory Szorc) — Thu, 16 May 2013 22:52:19 UT

This just landed in inbound. For variables where order isn't important
(pretty much everything except *DIRS), every incoming list append or
replacement must be sorted by byte order of the UTF-8 encoding of the
string (typically strings are ASCII). If it isn't, you'll see an error
message like:

Re: Deferred display of XUL panel containing embedded iframe

n...@parkwaycc.co.uk (Neil) — Thu, 16 May 2013 22:20:13 UT

display: none; destroys the nsIFrame object (in this case an
nsMenuPopupFrame), thus closing the panel.

--
Warning: May contain traces of nuts.

Re: Ordering shutdown observers?

bsm...@mozilla.com (Brian Smith) — Thu, 16 May 2013 21:18:56 UT

Many things (and an increasing number) depend on PSM/NSS and the PSM team (a long time ago) implemented its own shutdown event registration scheme (nsNSSShutDownObject in nsNSSShutDown.h). There seems like there is at least one race due to NSS being shut down while things are still using NSS which is causing a crash or worse (presumably because there is not enough awareness of the need to implement nsNSSShutDownObject and/or it is too error-prone to do so). Also, NSS must be shut down in profile-before-change because it may write to the profile directory.

Re: Persistently storing build system state

nalexan...@mozilla.com (Nick Alexander) — Thu, 16 May 2013 21:07:13 UT

Let me suggest another: keeping track of successfully built object
directories, so that remote testing commands can guess MOZ_HOST_BIN
candidates.

Nick

Re: Visual C++ PGO linker memory usage

bzbar...@mit.edu (Boris Zbarsky) — Thu, 16 May 2013 21:03:41 UT

This is awesome. Thank you, Ehsan and Ted, for getting this sorted out!

-Boris

Re: Persistently storing build system state

nalexan...@mozilla.com (Nick Alexander) — Thu, 16 May 2013 20:54:52 UT

I also think we should tap this potential. But:

Some of the things you mention are truly global: mach configuration, hg
extensions. But some things are more source-tree specific: build logs,
compiler warnings, test results. I would not want to share too much
state between my mozilla-inbound, mozilla-central, and services-central

Re: Visual C++ PGO linker memory usage

m...@glandium.org (Mike Hommey) — Thu, 16 May 2013 20:48:48 UT

They also mentioned having fixed some memory usage issues, so this also
will help in the meantime, provided they release these fixes some day.

Mike