Hi dev-platform,
We had a session about shutdown problems during the London workweek. I
did a writeup of what was discussed and as it grew into a large-ish
piece, I put it in a wiki page (instead of the email I intended to send
initially) [1].
There's been a lot of work on reducing shutdown crashe
Summary:
Load a specified URL in a controlled client page. Part of the service
workers spec
Bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1218148
Link to standard:
https://www.w3.org/TR/service-workers/#client-navigate-method
Platform coverage:
All platforms
Estimated or target release:
Fir
This is live in today's nightly. Again, please let me know if you run into
problems.
Thanks!
Ben
On Tue, Jun 28, 2016 at 3:01 PM, Ben Kelly wrote:
> Hi all,
>
> Please be aware I'm going to try enabling this pref on nightly later today:
>
> osfile.reset_worker_delay
>
> This will allow us to
On Thu, Jun 30, 2016, at 04:35 PM, smaug wrote:
> Not sure if this matters here, but cycle collector doesn't really retain
> objects. Sure, we could explicitly clear so called jsholders, so that
> C++->JS
> edges are manually cut. But in general, CC doesn't know about a cycle
> collectable objects
Did the now-defunct exit(0) project ever come up in this discussion?
See bugs 662444 and 826143. This was a perf team project back in the
Snappy days where the objective was to write important data to disk
ASAP, then exit(0) without doing a bunch of cleanup. The argument for
this was that, yes
There were plenty of blockers for _exit(0), including the fact that
pretty much none of the async code in Firefox/Gecko was shutdown-safe.
That's one of the reasons we had to come up with
nsIAsyncShutdown/AsyncShutdown.jsm. One of the not-entirely-stated goals
was that once everything registered w
Cool, thanks for the refresh on those details. Clearly this still
involves a bunch of work, but so would any other shutdown improvement
project.
My concern is that if we are going to reexamine shutdown, then I think
that exit(0) needs to fit into this somehow. If we're going to spend the
reso
On Thu, Jun 30, 2016 at 8:41 AM, Aaron Klotz wrote:
> Did the now-defunct exit(0) project ever come up in this discussion?
>
> See bugs 662444 and 826143. This was a perf team project back in the
> Snappy days where the objective was to write important data to disk ASAP,
> then exit(0) without do
On 06/28/16 01:01, Tanvi Vyas wrote:
Is it possible to safely redirect mxr to dxr?
This would be most welcome. There are lots of pasted MXR links
in Bugzilla comments which now requires tedious editing to
follow.
/Mats
___
dev-platform mailing list
Can we please automatically redirect from
https://mxr.mozilla.org/mozilla-central/source/x/y.z to
https://dxr.mozilla.org/mozilla-central/source/x/y.z? My browsing history
is littered with mxr URLs which used to make it very easy to find a file by
typing part of the name. As it stands all those URL
On 06/30/2016 11:49 AM, Nicolas Silva wrote:
Hi dev-platform,
We had a session about shutdown problems during the London workweek. I
did a writeup of what was discussed and as it grew into a large-ish
piece, I put it in a wiki page (instead of the email I intended to send
initially) [1].
There's
Hi Aaron, others,
On Thu, Jun 30, 2016 at 8:41 AM, Aaron Klotz wrote:
> Did the now-defunct exit(0) project ever come up in this discussion?
>
> See bugs 662444 and 826143. This was a perf team project back in the
> Snappy days where the objective was to write important data to disk ASAP,
> then
As part of a larger effort to improve the experience around debugging
intermittents, I've been looking at reducing the time it takes for
common "try" workloads for developers (so that e.g. retriggering a job
to reproduce a failure can happen faster).
Of course, the common advice of "profile be
Hi, Kendall. As a pain mitigation strategy for MXR URLs embedded immutably in
Bugzilla and in people's Awesomebar histories, can we redirect MXR requests as
Dão suggests? Some won't work, but many will, and those people will be less sad.
> On Jun 30, 2016, at 10:20 , Dão Gottwald wrote:
>
> Ca
Hello all,
Until now, adding jobs to Treeherder was completely opaque.
As of today you will see a "Sch" job start running soon after you make
your request.
You will have access to logs and a link to file a bugs. Filing bugs will
help when my alerting system does not catch issues.
I have all
On Thu, Jun 30, 2016 at 7:20 AM, Dão Gottwald wrote:
> Can we please automatically redirect from
> https://mxr.mozilla.org/mozilla-central/source/x/y.z to
> https://dxr.mozilla.org/mozilla-central/source/x/y.z? My browsing history
> is littered with mxr URLs which used to make it very easy to fin
In theory responses 301 and 308 mean "permanent redirect" so the browser
could do that for those responses.
In practice you'd need a lot of data to convince yourself that Web
developers haven't screwed this up too badly. Maybe 308, being newer, is
not compromised...
Rob
--
lbir ye,ea yer.tnietoe
On Fri, Jul 1, 2016 at 9:55 AM, Robert O'Callahan wrote:
> In theory responses 301 and 308 mean "permanent redirect" so the browser
> could do that for those responses.
Those would only work for as long as the 3xx is remembered, and it
wouldn't work for /x if you have only seen /y redirect.
To g
On Thu, Jun 30, 2016 at 04:49:26PM -0700, Gregory Szorc wrote:
> On Thu, Jun 30, 2016 at 7:20 AM, Dão Gottwald wrote:
>
> > Can we please automatically redirect from
> > https://mxr.mozilla.org/mozilla-central/source/x/y.z to
> > https://dxr.mozilla.org/mozilla-central/source/x/y.z? My browsing h
On Thu, Jun 30, 2016 at 4:55 PM, Robert O'Callahan
wrote:
>
> In theory responses 301 and 308 mean "permanent redirect" so the browser
> could do that for those responses.
>
> In practice you'd need a lot of data to convince yourself that Web
> developers haven't screwed this up too badly. Maybe
I recently started using Windows as my main development environment
(because that's what most Firefox users use and I want to improve the
Firefox development experience on Windows so more people develop on
Windows). It seems every day I find another source of painful slowdowns and
productivity issu
On Tue, May 31, 2016 at 4:22 PM, Gregory Szorc wrote:
> Heads up: we'll soon be dropping support for building mozilla-central with
> VS2013. Bug 1186064 tracks and the patch has already received r+.
>
> I'm going to wait a few days before landing because this could be
> disruptive and I want to a
This reminds me of a password manager bug we fixed 9 years ago (379997!),
where password manager would "helpfully" delete a saved HTTP login if it
got a 403 response upon using it. Unsurprisingly, this was a a terrible
idea that caused your saved logins to disappear when a site was glitchy.
Seem l
Gregory,
Le 1 juil. 2016 à 09:33, Gregory Szorc a écrit :
> I want the site to publish a "URL translation map"
> for URL patterns so whole URL namespaces can be bulk updated.
Interesting idea.
Probably something to explain in a wiki page somewhere on
https://wiki.mozilla.org/ with use cases an
William Lachance writes:
> As part of a larger effort to improve the experience around
> debugging intermittents, I've been looking at reducing the time it
> takes for common "try" workloads for developers (so that
> e.g. retriggering a job to reproduce a failure can happen faster).
> Also, accou
Adding Firefox source directory to Windows Defender's exclusion list is the
very first thing I do after I install the system. I also added the
directory of MozillaBuild to the list, and the C++ compiler (cl.exe) to
exclusion processes list. Not sure to what extend would that affect the
build speed,
On Fri, Jul 1, 2016 at 1:02 PM, Karl Tomlinson wrote:
> William Lachance writes:
>
> > As part of a larger effort to improve the experience around
> > debugging intermittents, I've been looking at reducing the time it
> > takes for common "try" workloads for developers (so that
> > e.g. retrigger
27 matches
Mail list logo