BETA

Transvision

Displaying 16 results for the string stack in nn-NO:

Entity nn-NO en-US
Entity # all locales browser • pdfviewer • viewer.properties
error_stack
nn-NO
Stakk: {{stack}}
en-US
Stack: {{stack}}
Entity # all locales devtools • client • debugger.properties
callStack.header
nn-NO
Call Stack
en-US
Call stack
Entity # all locales devtools • client • debugger.properties
copyStackTrace
nn-NO
Copy Stack Trace
en-US
Copy stack trace
Entity # all locales devtools • client • debugger.properties
variablesViewErrorStacktrace
nn-NO
Stack trace:
en-US
Stack trace:
Entity # all locales devtools • client • markers.properties
marker.field.endStack
nn-NO
Stack at end:
en-US
Stack at end:
Entity # all locales devtools • client • markers.properties
marker.field.stack
nn-NO
Stack:
en-US
Stack:
Entity # all locales devtools • client • markers.properties
marker.field.startStack
nn-NO
Stack at start:
en-US
Stack at start:
Entity # all locales devtools • client • memory.properties
censusDisplays.allocationStack.tooltip
nn-NO
Group items by the JavaScript stack recorded when the object was allocated
en-US
Group items by the JavaScript stack recorded when the object was allocated
Entity # all locales devtools • client • memory.properties
censusDisplays.invertedAllocationStack.tooltip
nn-NO
Group items by the inverted JavaScript call stack recorded when the object was created
en-US
Group items by the inverted JavaScript call stack recorded when the object was created
Entity # all locales devtools • client • memory.properties
checkbox.recordAllocationStacks.tooltip
nn-NO
Toggle the recording of allocation stacks. Subsequent heap snapshots will be able to label and group objects created when allocation stack recording is active by their allocation stack. Recording allocation stacks has a performance overhead.
en-US
Toggle the recording of the call stack of when an object was allocated. Subsequent snapshots will be able to group and label objects by call stacks, but only with those objects created after toggling this option. Recording call stacks has a performance overhead.
Entity # all locales devtools • client • memory.properties
dominatorTreeDisplays.allocationStack.tooltip
nn-NO
Label objects by the JavaScript stack recorded when it was allocated
en-US
Label objects by the JavaScript stack recorded when it was allocated
Entity # all locales devtools • client • memory.properties
tree-item.nostack
nn-NO
(no stack available)
en-US
(no stack available)
Entity # all locales devtools • client • netmonitor.properties
netmonitor.tab.stackTrace
nn-NO
Stack Trace
en-US
Stack Trace
Entity # all locales devtools • client • performance.dtd
performanceUI.table.samples.tooltip
nn-NO
The number of times this function was on the stack when the profiler took a sample.
en-US
The number of times this function was on the stack when the profiler took a sample.
Entity # all locales devtools • client • performance.dtd
performanceUI.toolbar.js-flamegraph.tooltiptext
nn-NO
Shows the JavaScript call stack over the course of the recording.
en-US
Shows the JavaScript call stack over the course of the recording.
Entity # all locales dom • chrome • layout • htmlparser.properties
errNoCheckUnclosedElementsOnStack
nn-NO
Unclosed elements on stack.
en-US
Unclosed elements on stack.

Displaying 20 results for the string stack in en-US:

Entity nn-NO en-US
Entity # all locales browser • pdfviewer • viewer.properties
error_stack
nn-NO
Stakk: {{stack}}
en-US
Stack: {{stack}}
Entity # all locales devtools • client • debugger.properties
callStack.header
nn-NO
Call Stack
en-US
Call stack
Entity # all locales devtools • client • debugger.properties
copyStackTrace
nn-NO
Copy Stack Trace
en-US
Copy stack trace
Entity # all locales devtools • client • debugger.properties
variablesViewErrorStacktrace
nn-NO
Stack trace:
en-US
Stack trace:
Entity # all locales devtools • client • markers.properties
marker.field.endStack
nn-NO
Stack at end:
en-US
Stack at end:
Entity # all locales devtools • client • markers.properties
marker.field.stack
nn-NO
Stack:
en-US
Stack:
Entity # all locales devtools • client • markers.properties
marker.field.startStack
nn-NO
Stack at start:
en-US
Stack at start:
Entity # all locales devtools • client • memory.properties
censusDisplays.allocationStack.tooltip
nn-NO
Group items by the JavaScript stack recorded when the object was allocated
en-US
Group items by the JavaScript stack recorded when the object was allocated
Entity # all locales devtools • client • memory.properties
censusDisplays.invertedAllocationStack.tooltip
nn-NO
Group items by the inverted JavaScript call stack recorded when the object was created
en-US
Group items by the inverted JavaScript call stack recorded when the object was created
Entity # all locales devtools • client • memory.properties
checkbox.recordAllocationStacks.tooltip
nn-NO
Toggle the recording of allocation stacks. Subsequent heap snapshots will be able to label and group objects created when allocation stack recording is active by their allocation stack. Recording allocation stacks has a performance overhead.
en-US
Toggle the recording of the call stack of when an object was allocated. Subsequent snapshots will be able to group and label objects by call stacks, but only with those objects created after toggling this option. Recording call stacks has a performance overhead.
Entity # all locales devtools • client • memory.properties
dominatorTreeDisplays.allocationStack.tooltip
nn-NO
Label objects by the JavaScript stack recorded when it was allocated
en-US
Label objects by the JavaScript stack recorded when it was allocated
Entity # all locales devtools • client • memory.properties
tree-item.nostack
nn-NO
(no stack available)
en-US
(no stack available)
Entity # all locales devtools • client • netmonitor.properties
netmonitor.tab.stackTrace
nn-NO
Stack Trace
en-US
Stack Trace
Entity # all locales devtools • client • performance.dtd
performanceUI.table.samples.tooltip
nn-NO
The number of times this function was on the stack when the profiler took a sample.
en-US
The number of times this function was on the stack when the profiler took a sample.
Entity # all locales devtools • client • performance.dtd
performanceUI.toolbar.js-flamegraph.tooltiptext
nn-NO
Shows the JavaScript call stack over the course of the recording.
en-US
Shows the JavaScript call stack over the course of the recording.
Entity # all locales dom • chrome • layout • htmlparser.properties
errNoCheckUnclosedElementsOnStack
nn-NO
Unclosed elements on stack.
en-US
Unclosed elements on stack.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.munger.talkback-link.help
nn-NO
Warning: Source string is missing
en-US
Makes ChatZilla hyperlink "TB<numbers><character>" to the specified talkback stack trace.
Entity # all locales mobile • android • chrome • browser.properties
stacktrace.outputMessage
nn-NO
Stakkdump frå %S, funksjon %S, linje %S.
en-US
Stack trace from %S, function %S, line %S.
Entity # all locales toolkit • toolkit • about • aboutTelemetry.ftl
about-telemetry-hide-stack-symbols
nn-NO
Vis rå stackdata
en-US
Show raw stack data
Entity # all locales toolkit • toolkit • about • aboutTelemetry.ftl
about-telemetry-stack-title
nn-NO
Stakk:
en-US
Stack:
Please enable JavaScript. Some features won't be available without it.