| /third_party/openssl/test/ |
| D | memleaktest.c | 47 char *lost; in main() local
49 lost = OPENSSL_malloc(3); in main()
50 if (!TEST_ptr(lost)) in main()
53 strcpy(lost, "ab"); in main()
56 OPENSSL_free(lost); in main()
60 lost = NULL; in main()
|
| /third_party/mesa3d/src/vulkan/runtime/ |
| D | vk_device.h | 133 int lost; member
319 return p_atomic_read(&device->_lost.lost) > 0; in vk_device_is_lost_no_report()
325 int lost = vk_device_is_lost_no_report(device); in vk_device_is_lost() local
326 if (unlikely(lost && !device->_lost.reported)) in vk_device_is_lost()
328 return lost; in vk_device_is_lost()
|
| D | vk_queue.h | 103 int lost; member
191 return queue->_lost.lost; in vk_queue_is_lost()
|
| /third_party/flutter/skia/third_party/externals/angle2/extensions/ |
| D | EGL_ANGLE_device_creation_d3d11.txt | 79 "If a Direct3D 11 device used to create a device experiences a "lost device"
81 undefined. It is the caller's responsibility to monitor for "lost device"
83 more information on "lost device", see the Direct3D documentation."
|
| /third_party/skia/third_party/externals/angle2/extensions/ |
| D | EGL_ANGLE_device_creation_d3d11.txt | 79 "If a Direct3D 11 device used to create a device experiences a "lost device"
81 undefined. It is the caller's responsibility to monitor for "lost device"
83 more information on "lost device", see the Direct3D documentation."
|
| /third_party/node/doc/guides/ |
| D | investigating_native_memory_leak.md | 77 ==28993== definitely lost: 0 bytes in 0 blocks
78 ==28993== indirectly lost: 0 bytes in 0 blocks
79 ==28993== possibly lost: 304 bytes in 1 blocks
170 ==1504== definitely lost: 996,064 bytes in 997 blocks
171 ==1504== indirectly lost: 0 bytes in 0 blocks
172 ==1504== possibly lost: 3,304 bytes in 4 blocks
185 definitely lost and the question is how to find where that memory was
221 ==4174== 64 bytes in 1 blocks are definitely lost in loss record 17 of 35
236 ==4174== 304 bytes in 1 blocks are possibly lost in loss record 27 of 35
249 ==4174== 2,000 bytes in 2 blocks are possibly lost in loss record 33 of 35
[all …]
|
| /third_party/openGLES/extensions/NV/ |
| D | NV_robustness_video_memory_purge.txt | 47 (FBOs), will be lost. As the OpenGL specification makes no mention
53 memory content has been lost, so that the application can re-populate
115 memory content has been lost. This will only take effect if the
128 memory content has been lost. This will only take effect if the
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/NV/ |
| D | NV_robustness_video_memory_purge.txt | 47 (FBOs), will be lost. As the OpenGL specification makes no mention
53 memory content has been lost, so that the application can re-populate
115 memory content has been lost. This will only take effect if the
128 memory content has been lost. This will only take effect if the
|
| /third_party/flutter/flutter/packages/flutter/lib/src/rendering/ |
| D | performance_overlay.dart | 21 /// step exceeds the frame slice, a frame is lost.
27 /// the bar turns red, a frame is lost.
35 /// this step exceeds the frame slice, a frame is lost.
41 /// turns red, a frame is lost.
|
| /third_party/flutter/flutter/packages/flutter/lib/src/widgets/ |
| D | visibility.dart | 95 /// (specifically, the state will be lost regardless of the state of
119 /// subtree to be lost (and a new instance of the subtree, with new [State]
142 /// subtree to be lost (and a new instance of the subtree, with new [State]
164 /// subtree to be lost (and a new instance of the subtree, with new [State]
184 /// subtree to be lost (and a new instance of the subtree, with new [State]
197 /// subtree to be lost (and a new instance of the subtree, with new [State]
|
| /third_party/rust/crates/peeking_take_while/ |
| D | README.md | 15 `false`, and it will be lost.
51 // ...except, when using plain old `take_while` we lost 10!
|
| /third_party/openGLES/extensions/ARB/ |
| D | WGL_ARB_pbuffer.txt | 68 4. The pixel buffer might be lost if a display mode change occurs.
315 pixel buffer memory was lost due to a display mode change. A value
316 of TRUE is returned in <iAttribute> if the display mode change lost
322 the pixel buffer memory has been lost. A value of FALSE is
370 - Changed the lost definition of a pixel buffer.
377 pbuffer may be lost due to a display mode change.
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
| D | WGL_ARB_pbuffer.txt | 58 4. The pixel buffer might be lost if a display mode change occurs.
305 pixel buffer memory was lost due to a display mode change. A value
306 of TRUE is returned in <iAttribute> if the display mode change lost
312 the pixel buffer memory has been lost. A value of FALSE is
360 - Changed the lost definition of a pixel buffer.
367 pbuffer may be lost due to a display mode change.
|
| /third_party/flutter/skia/site/user/sample/ |
| D | pdf.md | 47 - *SkImageFilter*: When SkImageFilter is expanded, text-as-text is lost.
58 - *drawTextOnPath* — expand. (Text-as-text is lost.)
|
| /third_party/skia/site/docs/user/sample/ |
| D | pdf.md | 48 - _SkImageFilter_: When SkImageFilter is expanded, text-as-text is lost.
58 - _drawTextOnPath_ — expand. (Text-as-text is lost.)
|
| /third_party/openGLES/extensions/KHR/ |
| D | KHR_robustness.txt | 194 CONTEXT_LOST Context has been lost Except as noted for
204 event, it is referred to as a <lost context> and is unusable for almost
206 all relevant state from the lost context. The current status of the
241 result in a lost context and require creating a new context as described
355 lost contexts.
480 11. What should the behavior of GL calls made after a context is lost be?
481 This can be expected to occur when the context has been lost, but the
489 features, so that apps can determine a context was lost and see the
505 commands on a lost context may not block) should not need exceptional
594 queries when contexts are lost (Bug 12104
[all …]
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/KHR/ |
| D | KHR_robustness.txt | 184 CONTEXT_LOST Context has been lost Except as noted for
194 event, it is referred to as a <lost context> and is unusable for almost
196 all relevant state from the lost context. The current status of the
231 result in a lost context and require creating a new context as described
345 lost contexts.
470 11. What should the behavior of GL calls made after a context is lost be?
471 This can be expected to occur when the context has been lost, but the
479 features, so that apps can determine a context was lost and see the
495 commands on a lost context may not block) should not need exceptional
584 queries when contexts are lost (Bug 12104
[all …]
|
| /third_party/ffmpeg/libavformat/ |
| D | rtpdec.c | 310 uint32_t lost; in ff_rtp_check_and_send_back_rr() local
347 lost = expected - stats->received; in ff_rtp_check_and_send_back_rr()
348 lost = FFMIN(lost, 0xffffff); // clamp it since it's only 24 bits... in ff_rtp_check_and_send_back_rr()
359 fraction = (fraction << 24) | lost; in ff_rtp_check_and_send_back_rr()
|
| /third_party/vk-gl-cts/build/external/vulkancts/framework/vulkan/ |
| D | vkPlatformFunctionPointers.inl | 2 * be lost! Modify the generating script instead.
|
| D | vkEntryPointValidation.inl | 2 * be lost! Modify the generating script instead.
|
| D | vkInitPlatformFunctionPointers.inl | 2 * be lost! Modify the generating script instead.
|
| D | vkInstanceExtensions.inl | 2 * be lost! Modify the generating script instead.
|
| /third_party/vk-gl-cts/framework/opengl/ |
| D | gluCallLogUtil.inl | 2 * be lost! Modify the generating script instead.
|
| /third_party/gstreamer/gstplugins_bad/sys/ipcpipeline/ |
| D | protocol.txt | 20 8: state lost
77 - 8: state lost
|
| /third_party/node/deps/npm/node_modules/verror/ |
| D | CHANGES.md | 17 * #39 captureStackTrace lost when inheriting from WError
|