s and what we calculate
from the values. We can then start tracking some of these in perfherder
and see if they’re stable enough to use as alerts.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform maili
would presume that such sites let you select
alternate versions to download already. And if not, they could, but
they might not bother/notice.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
;t deal with, or
deal poorly with, multi-process apps. No revelation here, of course.]
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ot obvious (it wasn't to me), 'file' is a keyword, not a
file to include, and all you really need to do is file a bug that blocks
bug 1543241 (or add that to an existing bug). We also should name that
bug, for easy in referencing in the future (I propose "mach-busted" ;-)
ably throw a lot of logs at it safely.
You can find them in the Marker Chart or Marker Table when viewing a
profile.
Now back to your regularly scheduled programming ;-)
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-p
current system kinda fell out of various
needs mostly around 20+ years ago and hadn't been revisted since then
really.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
>On 2/12/19 9:15 PM, Randell Jesup wrote:
>>> if you push to the Try server, use base revisions (= the shared revision on
>>> top of which you add your changes) from 2019-02-06 or newer, else there
>>> will be many test failures due to expired certificates. The new
show_bug.cgi?id=1525191
What if you need to push a Try involving an older rev (i.e. to verify a
problem or fix)? Is there a patch you can add on top of an older rev to
avoid failures?
Has the ESR branch been updated so it can be used as a base as well?
--
Randell Jesup, Mozilla Corp
remove &quo
s could impact webrtc calls or perhaps webrtc-based datachannel
applications (file transfers, games, etc, though likely if it's just
priority this won't be a problem).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
__
... and never realized I
could sort on modification status.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
t-only failures, or trying to verify if a regression identified in
mozregression for PGO was a PGO bug or now, though that could be checked
at the cost of a build or 4 even if we don't build opt, probably).
--
Randell Jesup, Mozilla Corp
remove "news&quo
n
# -n name is optional but recommended
hg qpop
Poof! that *should* be all.
Thanks to jkew, pehrsons, ehsan for suggestions!
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
e; may not be worth it).
Thanks! I'll let people know if it works
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
nt? (Some aren't and so perhaps I could do the sequence above for
each one, like the Dispatch queue with per-directory patches, but that's
not the common case.) Can we come up with a way to partially script
this, if there's a workable s
-no-remote
$ perf script -F +pid > /tmp/firefox.perf
Note that you'll want /proc/sys/kernel/perf_event_paranoid to be 1 (or
less).
To persist across reboots:
sudo sh -c 'echo kernel.perf_event_paranoid=1 >> /etc/sysctl.d/99.local.conf'
(or add to /etc/sysctl.conf, etc - wha
:
>> In the past, I believe we objected to adding WebP for various reasons.
>> Do we feel that those reasons are now outweighed by the compat problems?
(Personal opinion) Yes, unfortunately. And AV1F image format both isn't
ready and isn't universally supported; it will tak
>cd ~/.mozbuild && mach artifact toolchain --from-build linux64-tup
This doesn't work... no "mach" in my path. Going to a tree and typing
'./mach artifact toolchain --from-build linux64-tup' works though.
--
Randell Jesup, Mozilla Corp
remove "news"
ion and to a lesser extent for investigation
of responsiveness on specific pages, or for devtools (so developers can
see how their page is working). It's arguable how useful this is in
telemetry - though I think it might be worth tracking there, at least
for a while to compare.
--
Randell Je
Telemetry permission is an opt-out mechanism.
Right - this would need to be handled in a similar way to real crashes -
pop a crashreporter dialog to let the user submit it. We just wouldn't
kill the browser (and probably disable future semi-assertions until
restart once we hit
ashreports. This
would be a bunch(?) of work in crashreporter - ted? It might be easy
invoke a crashreport sampling, and continue, but I suspect it's not, and
might be quite hard.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Ehsan wrote:
>On Tue, Sep 18, 2018 at 1:30 AM Randell Jesup wrote:
>> We already *need* to be stable in that case, given MOZ_RELEASE_ASSERT
>> (and normal just-because crashes). And as best I can tell, we are stable
>> (with regards to user profiles). Once upon a time we w
long it takes to process (since there is no
actual input event here).
Once we have some experience with this, we could propose it for the
Performance API WG.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ELEASE_ASSERT
(and normal just-because crashes). And as best I can tell, we are stable
(with regards to user profiles). Once upon a time we weren't (5(?)
years ago?)
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
d
, or (if there are a lot in the dir) the file level.
Then we can look with eyeballs and figure out what's up.
It might also be possible to use trace APIs to measure the cost of each
assertion... though the traces themselves might swamp most assertion
costs.
--
Randell Jesup, Mozilla Corp
r
his can be enabled incrementally once the build/config
infra and macros are in place; there are several options for that.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
A good module system is a much more useful and liberating thing to do.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
l of the exact same
>concerns you raise with regards to in-tree ownership tracking applies
>(however it would be worse as it's imposed by a system separate from the
>review/landing tooling).
Agreed. Moving those to in-tree lists is certainly a win over current.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
>On 13/07/2018 04:55, Randell Jesup wrote:
>> Correct - we need to have observers/what-have-you for
>> background/foreground state (and we may want an intermediate state or
>> two - foreground-but-not-focused (for example a visible window that
>> isn't the focused
probably. hashtable->Finalize()? (I wonder if
that would let us make any other memory/speed optimizations if we know
the table is now static.)
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
e
gamed/wallpapered (assign a review to both the non-peer and a peer who
doesn't really review or reviews-the-review, etc), but that adds pain
and time and unneeded process.
Some modules (i.e. DOM) already to have a hard requirement for peer
review. That should be continued and should be
>On 07/12/2018 11:08 PM, Randell Jesup wrote:
>> We may need to trade first-load time against memory use by lazy-initing
>> more things than now, though we did quite a bit on that already for
>> reducing startup time.
>
>One thing to remember that some of the c
te a bit on that already for
reducing startup time.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
n
between processes. How large an impact this is I'm not 100% sure at
this point. If we changed sampling to be runtime-based instead of
wallclock-based, this (mostly) hides the impact of other processes,
though secondary effects still exist (cache impacts, etc).
Making it runtime-based would be
it, so I don't know how "hard" it is).
We'll have to do more than just limit process sizes, but limiting
process sizes is basically table stakes, IMO.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
e for example
remotes much of that to the master process.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
code to use your transport protocol instead of UDP via
IPC to the SocketTransportThread in the main process.
Note that there's a lot of code that implements ICE to determine what
ports are open, etc. That may complicate what you're doing.
If you want to do more than personal/local experimentation, mu
break webrtc to understand if it is compiled or not (in
>particular media/webrtc/trunk/webrtc/pc/channel.cc), but i did not receive
>errors.
We don't use (or compile) all the imported webrtc code.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
_
on.
>
>Happy sanitizing!
A late response, but this is truly awesome.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
lso (as others have pointed out) going too far back (often not that
far) may run you into tool differences that break re-building old revs.
Hopefully you don't get variable behavior, just a failure-to-build at
some point. I'm not sure how much Rust has made this worse.
--
Randell
bout
this, and how to get real data when interaction occurs reliably.)
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
of a merge date). 99% of the time when I ask for N
people, I need r+ from all of them.
On the other side, I do know that the build peers (IIRC) us a shared
reviewing setup, where most bugs are thrown in a pool for any of them to
review. But that's not the normal workflow for any other group
peline/dist.html#!cumulative=0&end_date=2018-03-01&keys=__none__!__none__!__none__&max_channel_version=beta%252F59&measure=USE_COUNTER2_DEPRECATED_URLCreateObjectURL_MediaStream_PAGE&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2017-11-13&table=0&trim=1&use_submission_date=0
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
n't find where
>>> at the moment).
>>>
>>> There is official documentation at https://secure.phabricator.
>>> com/book/phabricator/ which is linked from our Mozilla-specific docs (
>>> http://moz-conduit.readthedocs.io/en/la
e a lot of events (and a number of objects) defined for
WebRTC as part of dom/media/PeerConnection.js
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
res building a
"standard" config, which many do not). Leveraging local background
builds would be much easier in many ways, though also less of a win.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
__
say it's not worth the risk. Or
allow it, but only with commentary as to why it's safe, or with rules
about what sort of types it's allowed with and anything other than those
requires justification in comments/etc.
--
Randell Jesup, Mozilla Corp
remove "news" for per
ear enough space to ccache, though.
Rotating disks are cheap (and easy if you have a desktop; less so though
not horrible if you have a a laptop, especially with a dock). They
don't necessarily solve Boris's problem, however. He could really use a
1TB SSD I suspect.
When I got my cur
g with a report about a problem
won't go looking. Something that proactively can poke them is far more
likely to get action.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ere it was before I scrolled down - and stayed stable. (Note: I hit
reload with the current position near the bottom with 1 ad visible (no
video).
Using an additional GB+ of memory in order to free 1GB of memory
seems... excessive.
--
Randell Jesup, Mozilla Corp
erformance can be useful, but 3 tabs vs all tabs is too coarse
for me, and things like "site leaked memory and is slowing CC" I presume
doesn't show up in the 'heat' for the tab there.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
though I'd like to see the ID back on Nightly at least - makes starting
GDB against the right content process *much* easier, and I don't have to
limit the browser to 1 to avoid the problem.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
a static-analysis bit
was needed after hitting and solving a few (or a bunch of) crashes/sec bugs --
static-analysis tends to be reactive.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
f? probably not a lot unless you're super-focused on Rust code,
but that's just a guess.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
>SGTM. BTW, bug 143038 was filed 16 years ago. Is that a bugzilla record for
>oldest fixed bug?
Not even close I think... a couple of years ago I remember some low-4-digit
bugs getting fixed (maybe even a 3-digit?) :-)
--
Randell Jesup, Mozilla Corp
remove "news" fo
all users. Extensions can help here, modulo most users don't look for
them. You could also offer that (extension or option) when they import
profile data from Chrome, or put a link in Prefs to a Chrome-like tab
WebExtension (Prefs *could* have links to relevant Extensions).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
port "groups" of hidden tabs, the
>tableau visualization was great for managing overstuffed windows and
>quickly culling the tabs spawned during some now-complete task or research.
yes! I actually often cull tabs from session-restore (vertical list
with titles!) or from about:
't
communicated (or discussed!) well, since 58 is already open...
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
agree with Mats here - it's easier to read, specifically in the case
where you have a large number of args, especially of widely varying
type-lengths. Obviously, one could disagree, but that's a good example.
--
Randell Jesup, Mozilla Corp
remove "news" for personal ema
;t "mochitest-media" (and other non-e10s
versions) be not-run by default, unless you specify it explicitly in -u ?
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists
onal syncing - your point about being able to
look at the bug and know who can see it is important, but I don't see
any advantage in subscribe mirroring into cc. I would (as you suggest)
block subscribe on sec issues, to avoid confusion (if you can, tell
people to use cc, but that's just
ov !pgo 'reftest !jsreftest"
> - ./mach try --preset reftest
Also really great.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
> - We found out that MediaStreamGraphStableStateRunnable is #20 on this
> list, which was surprising as this runnable is only supposed to be used for
> WebRTC and WebAudio, neither being extremely popular features on the Web.
> Randell Jesup found out that there is a bu
always. It's needed.
Another aspect of all this that needs to be thought out and verified is
what happens when a non-sec bug becomes a sec bug (and vice-versa,
though I'm far less concerned about that). When a bug becomes a sec
bug, all patches associated with
e our
discussion in May, and have you met with the security engineers and
major security reviewers/triagers?
Thanks
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
abricator is a viable option, nor
making it less-featured, so we may have to eat the pain and lash people
with wet noodles if they post in the "wrong" place.
--
Randell Jesup, Mozilla Corp
remove ".news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ort term, or that it won't end up slowing
down N*100 developers, either for a while or permanently. And the lack
of transparency in developing this plan is also very concerning.
IMO
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ricator backed products, we could
>make it a read-only patch viewer.
I would consider it a massive fail if we disabled at least read-only
splinter viewing of patches. As noted before. let's make sure we
don't lose things we agreed on as issues.
--
Randell Jesup, Mozilla Corp
re
>On Monday, July 10, 2017 at 3:28:07 PM UTC+12, Randell Jesup wrote:
>I added these stats originally, and they are now mostly superseded by the
>stats provided by VideoPlaybackQuality. So I support their removal (in fact
>I suggested to Tim that he remove them).
>
>Adding tele
should* in theory avoid the consistency problem, and only annoy
users without reason in the odd case where the moved their profile(s).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
mozPaintedFrames). There is one test using mozParsedFrames.
Before landing any deprecation warnings, you should check with the
media/webrtc teams, and we may want to check how one or two external
users are using it.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
ble on 10.7 SDK,
and we can't use certain newer features/APIs because of it.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
> [2] https://crash-stats.mozilla.com/signature/?product=
>> Firefox&release_channel=release&signature=BaseThreadInitThunk&date=%3E%
>> 3D2016-12-05T14%3A42%3A31.000Z&date=%3C2017-06-05T14%3A42%3A31.000Z#graphs
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
other large companies
>do here.
>
>I hope this post doesn't revive this thread and apologize in advance if it
>does. Please consider replying privately instead of poking the bear.
I did consider it. But I can't be quiet publicly with a posting stating
"this *will* happen" (emphasis added) on the table.
I certainly know of the vulnerabilities here but I also see how much
friction for our development cycle might be caused, with little
real-world benefit (IMHO). The last thing we need is to move a lot slower.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
t up a Wiki page on all this soon.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
e), and/or the cooling solution is causing thermal throttling -
mobile CPUs often can't run all-cores-flat-out for long in typical
laptop cooling.
Windows builds slower. Of course.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
__
that analysis and discussions with people involved
(Media/WebRTC/Networking/Sandboxing teams).
The full document with details on the pluses and minuses of each option
is here:
https://docs.google.com/document/d/1cwc153l1Vo6CDuzCf7M7WbfFyHLqOcPq3JMwwYuJMRQ
Randell Jesup
Media, WebRTC and Ne
would like to see the API in Firefox.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ted in DTMF support since they're
generally PBX/IP-phones and SIP trunking/etc people.
Apple of course never says anything, but they're clearly working on
WebRTC support.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
_
, and more likely move towards Pulse ("users" are more likely to
be running plain-jane distros which have Pulse enabled by default - but
we'll see).
We'll start getting beta results in a few weeks.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
t; to try
>for anytime soon.
Likely so, though I'll note that Jack support for cubeb + Firefox has
recently been updated by a contributor; so you can build with a Jack
backend (or so I understand; I haven't tried it).
Padenot or achronop can tell you more about this.
--
Randell Jesup, Mozil
ng that noticably ups the load on
infra when there's a low chance of catching something is a bad trade.
Of course, this depends on the devs being smart about what they skip
try/autoland on (for example, nit-fix changes are a good choice - usually).
--
R
ber the more times
you do something. (Which includes leaks-occasionally-due-race).
One-off leaks (leak of a single pre-process instance of something) are
at most an annoyance unless large or eating CPU.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
_
Hello through Go Faster. The Go Faster process allows us to
>uplift directly to Beta 46 directly since we're a system add-on
>(development was done about 2 weeks ago).
>Firefox Hello has its own privacy notice (details here
><https://www.mozilla.org/en-US/privacy/firefox-hel
>On 2/27/2016 9:06 PM, Randell Jesup wrote:
>> months until recently it popped up a bit). Note that this failure
>> *never* results in a crashdump, and I've never seen it locally, just in
>> Automation.
>
>What we do know:
>
> * Exit code -11 is evidence a
ll-setup recreation of a real Try run.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b2eb01359621
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ies of tests to match
theirs, or vice-versa, just to check which sites appear to care (and
then mark them).
Great! It'll be interesting to track how these change over time as well
(or as versions get added to the list). Again, medians/means/etc may
help with evaluating and tracking th
ld add DispatchFallible() (DispatchNeverLeaks()?) if that's a
wide-enough pattern; part of my question in that case is "did the caller
really expect Dispatch to possibly fail, and what implications does such
a failure have to the rest of the system?"
--
Randell Jesup, Mozilla
nts of the runnables might not be...
Sec bugs and crashes are worse than leaks, and they can occur
if we have non-testable random off-thread releases, which is what we
had, and still do for things not switched to already_AddRefed<>.
I'd be good with flagging/asserting on Dispatch fail
them change. That most certainly isn't everything, note.
One smart thing that *could* be done for automation (and save a *bunch*
of VM/tester time) would be to not re-run cppunit tests that didn't get
rebuilt - since inbound/etc do incremental builds by default, many
checkins rebuild few or none of the cppunit tests, so running the same
executable again has limited value (not none, but limited).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
t the "ecosystem' of media
routing and ability to transform it (as we can with WebAudio &
MediaStreams).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ven't visited for a while. An
>> unloaded tab is restored back to its original state when you need it again.
>> """
"original state" likely doesn't include sites that dynamically modify
themselves, which is a lot of sites.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
; >restyles etc.
>> I think Chris might want to follow the history of a particular line,
>> that is usually what we use flame for. I find |git gui blame |
>> very useful.
>
>Just to clarify what I meant by "visually scrub through blame history",
>h
>On Sat, May 23, 2015 at 4:46 AM, Randell Jesup wrote:
>> This is used extensively in WebRTC and related media bits to enable
>> *huge* amounts of debugs (like every-frame debugs for audio or video or
>> per-network-packet debugs, which will swamp a system normally), and sin
g confusion) compared to allowing a "PR_LOG_VERBOSE" level.
PR_LOG_VERBOSE is clear and understandable. Modules where normal debugs
are on INFO and you-likely-don't-want-it is on DEBUG will cause
ongoing mental anguish and mismatch, and confusion for new contributors.
>We
t, but not
>> horribly).
>
>I think it's probably best to keep this a separate env rather than trying to
>shoehorn it in.
Understandable - but I've been trying to move in the opposite direction;
avoiding N different env vars (and also, if I can avoid that, I have
a better
#x27;re faster to type/read and lots of existing scripts/etc have them.)
Obviously one could have numbers and names.
>As a future improvement we plan to add the ability to toggle this levels at
>runtime.
This would be wonderful! Been looking for that for years (and years).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ch?), and thus block all attempts to do
DispatchToMainThread(new FooRunnable), etc. :-)
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
d the major real problem was too-similar-names (I'd never heard of
STREAMTRANSPORTSERVICE (or if I had, it had been long-forgotten, or
mis-read as SOCKETTRANSPORTSERVICE)).
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
tartup probably (or use a static buffer). You still would have to
dynamically allocate one if the static buffer wasn't big enough, and
that could then fail of course.
Better than turning off >2GB memory, though.
--
Randell Jesup, Mozilla Corp
remove "news" for personal email
___
ocking operations
off of MainThread, it would help other modules to have a single service
or ThreadPool for dumping such operations to. This would mean less
code, less incorrect/undone thread shutdowns/etc. Thoughts? (Perhaps
such a service could use LazyIdleThreads, which will shut themselves
d
1 - 100 of 127 matches
Mail list logo