►
From YouTube: Node js Diagnostic working group meeting 5th April 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
Yeah
that
issue
was
submitted
by
me
and
the
main
goal
of
the
program
is
that
currently
the
pro
books
provided
the
opportunity
that
I
mean
real
time
in
tracing
api.
Like
say,
we
can
use
the
global
performance,
dot
mark
and
the
global
performance
dot,
mario
to
measure
user
timings
of
their
events.
But
it's
there
is
no
space
to
name
space
support
in
this
market
and
measure.
So
it
is
very
easy
to
get
to
get
stepping
on
our
other
marks
and
measures
when
we
are
using
them
to
chase
our
server-side
server-style
events.
C
I
have
submitted
a
issue
to
the
w3c
to
discuss
the
problem
and
we
have
reached
a
consensus
that
the
when
there
are
interest
in
other
implementers
like
say
browsers
as
they
are
willing
to
try
out
adding
namespace
support
to
the
user
timing
api
and
so
that
they
can
introduce,
introduce
the
also
they
can
also
introduce
the
tracing
to
use
users
into
the
dev
tools
to
display
the
username
space
in
the
dev
tools.
So.
A
C
C
C
So
basically
the
problem
is
about
the
performance,
dot
mark
and
the
performance,
the
mirror
being
without
the
number
space
we
can
collide
with
it
with
each
other
in
a.
I
think,
it's
in
in
a
sync
event.
So
since
then,
I
think
we
can
have
like
say
have
multiple
facing
event
similar
same
everything
event
in
parallel
and
they
can
have.
C
They
can
try
to
visit
with
each
other
since
they
have
the
same
names.
So
that's
the
problem
on
the
issue,
so
I'm
I'm
submitting
the
since
we
have
a
very
brief
early
consensus
on
the
wcc
opening
group.
So
I'm
submitting
the
issue
to
node.js
to
see
if
there
are
interests
or
any
feedbacks
to
the
idea
of
this
problem
and
I'm
supposed
to,
we
are
going
to
draft
the
stack
changes
to
the
timing
of
the
cc
working
group.
C
C
A
Really
great
problem
to
solve,
but
just
trying
to
understand
some
of
the
details.
For
example,
when
you
say
the
performance
entries
are
going
to
be
created
again
and
again
with
the
same
name,
is
it
by
the
same
program
hitting
the
same
name
and
again
because
you're
running
in
a
loop
kind
of
thing,
or
is
it
by
different
programs
belonging
to
different
npm
modules
using
the
same
name
colliding?
Yes,.
B
C
Yeah
right-
and
we
don't
have
to
cl
significantly-
is
that
when
we
want
to
clear
entries
from
the
global
performance
timeline,
we
have
to
use
the
name
and
the
types
to
clear
the
entries.
So
that's
another
problem
with
the
name,
since
we
have
to
clear
the
entry
with
the
names
which
maybe
we
may
accidentally
remove
other
others
entries
with
the
same
name.
So
that's
that's.
That's
another
name
with
inclining.
C
D
C
C
D
So
so,
basically,
the
the
memory
leak
is
the
the
main,
the
main
issue
in
this
in
this
problem,
and
I
mean
for
we
have
a
way
of
measurement.
For
I
mean
if
I
forgot
to
to
clean
up
three
entries,
how
much
memory
I
I
am
leaking,
or
something
like
that
just
to
to
to
capture
how
much
what
is
the
if
it
is
critical
or
not
for
current
application
using
the
performancy
hooks,
you
know.
C
And
the
current
api
ship
is
designed
by
the
wcc
in
in
their
currently
usage
intent,
it's
for
the
browser
and
like
say
the
host
and
most
performance
engines,
since
they
are
never
getting
garbage
collected
since
it's
by
intent
and
when
the
problem
comes
to
the
user
timing
and
the
drawback
or
current
api
design
is
getting
more
significant
and
for
the
userland
performance
tracing.
Since
we
have
like
say
third-party
libraries
and
the
code,
we
are
not
controlled.
D
E
D
D
A
D
D
Yeah,
actually
I
I
have
a
question
that
situation,
because
there
are
some
tools
that
most
of
us
is
unaware.
I
mean
is
maintained
by
other
folk.
That
is
not
from
diagnostics,
so
we
don't.
We
don't
have
too
much
information
to
to
to
say
that
it
is
still
under
maintenance
or
nobody.
Nobody
use
it
anymore.
I
just
want
to
to
make
sure
that
we
have.
What
is
that
the
list
for
a
two
to
be
accepted?
D
A
So
the
tier
one
and
tier
two
qualifications
are
pretty
straightforward.
Tier
three
says
it's:
if
possible,
its
deceit
will
be
run,
at
least
in
nightly
of
the
node
jfci.
But,
interestingly,
none
of
these
qualifiers
mention
anything
about.
You
know
the
the
information
regarding
the
author
ship
or
any
source
of
information
pertinent
to
the
actual
debugging
tool.
A
If
I
remember
correctly,
the
previous
conversation
on
this
was
that
the
tool
doesn't
have
to
be
maintained
by
the
node.js
organization
doesn't
have
to
be
residing
in
any
of
our
post
it
as
long
as
these
conditions
are
met
like
it
has
a
a
suit.
It's
widely
used,
and
it's
it's
working
on
all
these
supported
platforms.
D
D
D
B
E
B
A
We
definitely
have
two
alternatives:
one
is
the
hipdam
tool
without
the
node
dash
prefix
to
it,
and
then
we
also
have
the
same
capability
integrated
into
the
node
code
as
an
api
which
is
under
the
v8.
So
what
the
npm
tool
used
to
do
is
basically
available
as
a
public
api
yeah,
there
may
be
very
thin
use
cases
wherein
you
you
would
want
to
run
it
as
a
module
versus
an
api.
I
I
don't
know
what
what
is
that
advantage
or
disadvantage,
but
yeah?
A
B
A
E
D
B
A
B
A
C
A
B
D
B
A
D
D
D
A
A
A
D
Following
question
here,
yeah,
actually,
my
concern
here
is
because
they
know
the
clinic
is
a
suite
of
tools.
You
know
it
contains
flame
grafts.
It
contains
a
hipped
up
and
a
lot
of
those
stuff
and
those
those
tools
have
third
part
dependence.
For
instance,
the
0x
is
a
tool
that
no
the
clinic
depends.
So
it
means
that
if
we
move
the
node
clinic
to
tier
1,
0x
will
be
probably
in
the
tier
1
as
well.
A
C
D
B
D
E
D
C
E
E
D
B
A
A
E
E
A
B
A
D
D
D
D
I
I
mean
this
is
my
my
point
of
view
looking
outside,
but
maybe
when
you
open
the
the
pr,
if
we
we
decide
to
remove
it,
we
we
can
discuss
about
it
but
yeah.
For
me,
I
don't
think
that
there
is
a
way
to
support
it
in
tier
one,
because
it
is
basically
use
everything
from
from
v8
and
it
should
be
tested
there.
B
A
B
Yeah,
it's
yeah,
it's
my
point
also
that
sometimes
we
also
want
to
provide
documentation
and
stuff
like
that,
and
maybe
it's
enough
to
see
that.
Okay,
it's
a
target
because
people
could
use
it
it's
widely
used
and
we
want
to
provide
good
documentation
the
context
on
the
gs
to
use
it
or
maybe
it
already
exists.
I
don't
remember,
but
maybe
we
already
have
stuff
like
this.
B
A
D
We
have
several
guides
on
that
in
the
in
our
tutorials
in
the
diagnostic
repository
yeah,
maybe
target
a
tier
one
would
be
nice,
but
I
mean
my
my
real
concern
here
is
how
should
I,
how
should
I
support
these
two?
You
know
because
does
it
make
sense
to
me
to
to
to
node.js
create
tests
for
v8
for
chrome,
devtools
usage?
You
know
because
it's
it's
basically
v8.
You
know
you
cannot
v8
test
us,
but
not
us.
That's
v8.
You
know
yeah,
but.
B
My
point
wasn't
that
my
point
was
just
to
I
did.
I
said
that
we
want
to
target
the
tier
one
because
we
want.
We
don't
want
to
add
tests,
because
we
we
cannot
test
it
so
and
it's
more
like
we
could
provide
documentation
and
guides
so,
but
my
point
is
just
to
not
delete
it,
but
it's
not
too
full
supported
because,
as
you
mentioned,
your
points
are
I'm
okay.
With
your
points.
D
B
B
D
D
A
A
Yeah
this
one
looks
to
be
the
guy,
so
the
the
key
thing
is
time.
Travel
debugging
is
really
cool
stuff,
which
helps
you
move
backward
in
the
instance
of
the
executions
in
a
step-by-step
and
controlled
manner.
But
then,
if
it
is
relevant
only
in
the
chakra
core
javascript
engine,
which
is
absolutely.
D
D
D
E
B
B
I
don't
know
if
you
want
to
move
on
another
item,
but
I
want
just
to
mention
something
about
trace
gcc.
If
I
have
one
or
two
minutes
sure
yeah
so
recently
to
address
dc
to
to
the
list
and
then
add
a
few
tests
or
run
tests,
and
now
I
think
that
it
could
be
nice
to
have
a
guide
to
use
it,
and
I
just
want
to
share
with
you
and
know
if
you
have
doubt
or
if
you
want
to
give
me
for
insight.
B
My
point
of
view
was
that,
as
when
you
run
this
comment,
you
have
mark
sweep
scavenge
events,
and
probably
people
are
a
bit
scary
of
meaning
of
this
stuff.
So
it
could
be
start
with
a
little
guide.
To
just
give
you
insight
and
explain
how
we
could
use
strategy
to,
for
example,
try
to
support
memory
leak
or
if
we
think
that
he
could
have
a
radix.
And
then,
if
we
see
that
we
have
a
few
mark
super
version
that
doesn't
clean
memory,
then
you
could
have
a
memory
them
too
fine
and
stuff
like
that.