> On 25 Apr 2019, at 8:49 am, Bobby Holley <bobbyhol...@gmail.com> wrote.
>>
>
> I think the tradeoff boils down to (a) how many developers are using
> non-e10s debugging, with what frequency, versus (b) how much ongoing
> maintenance work is required across various components to keep non-e10s
> working. We all have intuition about these things, but I doubt we have hard
> data.
>
> I'm open to the argument that my proposal is too aggressive. We could
> certainly try the muddle approach for a while and see how it goes, and how
> often 1proc breaks in practice. I don't think we can justify continuing to
> run the full suite of 1proc tests as tier-1, but we could potentially run a
> few smoketests, which might keep the builds usable enough for debugging.
>
> If anyone is chomping at the bit to remove 1proc support from their module,
> please speak up.
I am one of those developers that find non-e10s essential to debug core
features.
Debugging in e10s adds a big overhead in the effort required to determine on
the why something isn't working as it should.
When debugging HW specialised features (for media those are running in the GPU
process), in e10s you always hit timeouts that cause a cascade of failures
elsewhere.
Of course we can do without, but at the expense of time and convenience. Before
non-e10s support is removed, I'd love to see better development/debugging
tools, particularly on Windows added to help our workflow.
I knew this day would come, tbh I'm surprise non-e10s has lived for so long.
However, I don't believe my workflow is unique to whomever is working on gecko.
Jean-Yves
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
