Re: [dev-servo] Moving away from merge commits

On Wed, Apr 27, 2016 at 8:34 AM, Matt Brubeck wrote: > On Wed, Apr 27, 2016 at 7:25 AM, Manish Goregaokar > wrote: > > > Another reason I prefer merge commits is that it becomes very easy to > hunt > > down which PR caused a bug (after using blame or

Re: [dev-servo] Output profiling data as a timeline

On Tue, May 3, 2016 at 12:16 AM, Paul Rouget wrote: > This is awesome! > ​Great :)​ I'm under the impression that it stops profiling after the page has > loaded. Is that right? > ​It continues profiling from startup till shutdown.​

[dev-servo] Output profiling data as a timeline

As of https://github.com/servo/servo/pull/10694, you can dump the profiling data from the `components/profile/time.rs` module as a timeline in a self contained HTML file that is easy to share/upload/etc. Usage: $ ./mach run -r -p 5 --profiler-trace-path ~/output.html https://reddit.com/

Re: [dev-servo] A new approach to rooting SpiderMonkey types

Hi Ms2ger! Can you briefly summarize the new approach, contrast it to the old one, and describe how it solves the issues around moving? Thanks! Nick On Mon, Jun 27, 2016 at 1:21 AM, Ms2ger wrote: > [Cross-posting to m.d.t.j-e.internals; please reply only to m.d.servo.] > >

Re: [dev-servo] Servo contributor map

I see that you've found me ;) On Wed, Jul 6, 2016 at 7:15 PM, Shing Lyu wrote: > Hi all, > > I've made a few maps of the servo/servo contributors. > > https://flic.kr/s/aHskDBNv66 > > This is done by downloading the list of contributors from GitHub API, get > their locations

Re: [dev-servo] Servo contributor map

Err: > * 1 from "Right behind you" I see that you've found me ;) On Thu, Jul 7, 2016 at 11:02 AM, Nick Fitzgerald <nfitzger...@mozilla.com> wrote: > I see that you've found me ;) > > On Wed, Jul 6, 2016 at 7:15 PM, Shing Lyu <s...@mozilla.com> wrote: >

[dev-servo] How to smup?

What is the current workflow for doing a SpiderMonkey upgrade? Is this documented somewhere? Call `js/src/make-source-package.sh` and then untar the result into a `sevo/mozjs` checkout and manually reapply every upstream commit? (I really hope there is a less manual way...) When does bindgen get

Re: [dev-servo] What should be the unit of debugging in Servo?

I think that each unit of sequential execution should get its own debugger server (so a (same origin?) related browsing context). Then if we want to present a unified interface, we can race-ily pause workers (and cross origin iframes?) and coalesce these things in the UI or via a supervisor task.

Re: [dev-servo] Proposal: remove mingw Servo builds in favor of msvc

On Thu, Sep 8, 2016 at 10:32 AM, Lars Bergstrom wrote: > TBH, if SM > were available as a prebuilt static lib, we'd probably consider just > using that in the Servo build in order to save a bunch of build time > ​​ > and avoid the msys2 dependency. > ​This should be

Re: [dev-servo] Proposal: remove mingw Servo builds in favor of msvc

On Thu, Sep 8, 2016 at 10:55 AM, Gregory Szorc wrote: > ​ > This is almost certainly doable from the perspective of Firefox's > automation making those bits available as a side-effect of builds. ​I think we would want to make SM-tc(pkg) a static build -- it already is

Re: [dev-servo] Creating a JSObject -> id map for the Debugger IPC server.

We already have IDs for GC things that are stable across moving GCs, but I'm not 100% sure they are exposed in JSAPI. Aha, looks like it is exposed: http://searchfox.org/mozilla-central/rev/594937fec2e2fc45fa9308ba2fb964816631f017/js/public/RootingAPI.h#660 On Mon, Dec 12, 2016 at 9:10 PM, Jim

Re: [dev-servo] Plans for implementing progressive web metrics

Additionally, the existing profiling infrastructure can already dump its raw data as a TSV file. On Fri, Mar 31, 2017 at 1:51 PM, Josh Matthews wrote: > On 2017-03-31 4:38 PM, Jack Moffitt wrote: > >> Together, these metrics will give us information on the graphical

[dev-servo] Zhitin Zhu's intern presentation on Magic DOM

Hello Servo aficionados! On Thursday August 3rd at 2:30pm (PDT), Zhiting will be presenting his work on the ~*~ Magic DOM ~*~ project! Join us on https://air.mozilla.org/ to tune in :) See you there! Nick ___ dev-servo mailing list

Re: [dev-servo] Memory reporting in Servo: the next step

Hi Nick! The combination of deriving traits and Rust's ownership model is great for memory reporting, and this stuff is _so_ much nicer to define than the equivalent about:memory measurements in Firefox. But it doesn't play out as well in the presence of a GC: ownership is muddied. The Arc/Rc

Re: [dev-servo] Memory reporting in Servo: the next step

​On Fri, Oct 6, 2017 at 8:57 PM, Nicholas Nethercote wrote: > Memory reporting as done for about:memory is quite different to the memory > profiling done for devtools. > > Here's how memory reporting works in SpiderMonkey: we iterate over every > cell in the GC heap, and

[dev-servo] Rust bindings to SpiderMonkey on inbound

(cc dev-servo, dev-platfrom; reply to js-engine-internals) Hello everyone! The Rust bindings to SpiderMonkey that Servo uses just landed in mozilla-inbound[0]! You can monitor their test results on taskcluster as the `SM-tc[tier-2](rust)` job. If any of your patches break these tests, please