Searched refs:launched (Results 1 – 25 of 108) sorted by relevance
12345
| /third_party/flutter/flutter/dev/devicelab/bin/tasks/ |
| D | system_debug_ios.dart | 39 // When a debug-mode app is launched from the host there should be no warnings.
53 // When a debug-mode app is launched from Xcode there should be no warnings. The
74 // When a debug-mode app is launched from the home screen there should be a
|
| /third_party/node/tools/snapshot/ |
| D | README.md | 6 deserialized on top of V8's own startup snapshot. When Node.js is launched,
41 with Node.js snapshot embedded can also be launched without deserializing
|
| /third_party/boost/libs/fiber/doc/ |
| D | fiber.qbk | 53 Each __fiber__ represents a micro-thread which will be launched and managed
67 A new fiber is launched by passing an object of a callable type that can be
140 outlive the __fiber__ object that launched it, use the __detach__ method.
172 newly-launched fiber.
181 [[Effects:] [A fiber launched with `launch == dispatch` is entered
189 [[Effects:] [A fiber launched with `launch == post` is passed to the
191 previously-running fiber) continues executing. The newly-launched fiber will
590 from an explicitly-launched thread[s] thread-function. That is, in many
592 explicitly-launched fiber.
|
| D | migration.qbk | 20 launched, cannot migrate to any other thread. Also __boost_fiber__ implicitly
78 threads are launched.
|
| D | overview.qbk | 46 Control is cooperatively passed between fibers launched on a given thread. At
79 A fiber launched on a particular thread continues running on that thread
|
| D | future.qbk | 420 __StackAllocator__ when constructing the launched `fiber`. The overloads
422 constructing the launched `fiber`. The default `launch` is `post`, as
|
| D | packaged_task.qbk | 23 # Call [member_link fiber..detach] on the newly-launched `fiber`.
|
| D | customization.qbk | 53 the ones explicitly launched by instantiating a custom `fiber` subclass.
|
| /third_party/ffmpeg/ |
| D | INSTALL.md | 6 `configure` can be launched from a directory different from the FFmpeg
|
| /third_party/skia/third_party/externals/swiftshader/src/Reactor/ |
| D | reactor.gni | 19 …build LLVM on Mac, unless we have to. This only happens on ARM64 devices, which launched with 11.0.
|
| /third_party/flutter/flutter/packages/flutter_tools/doc/ |
| D | attach.md | 5 A Flutter-command that attaches to applications that have been launched
|
| /third_party/flutter/flutter/packages/flutter_tools/lib/src/test/ |
| D | watcher.dart | 34 /// The index assigned when the child process was launched.
|
| /third_party/python/Doc/library/ |
| D | getpass.rst | 33 terminal you launched IDLE from rather than the idle window itself.
|
| D | asyncio-policy.rst | 265 threads, doesn't interfere with any processes launched outside the event
266 loop, and scales linearly with the number of subprocesses launched by the
|
| /third_party/flutter/flutter/packages/flutter_tools/test/general.shard/web/ |
| D | web_fs_test.dart | 84 // Chrome is launched based on port from above.
|
| /third_party/glib/gio/tests/ |
| D | appinfo.c | 327 launched (GAppLaunchContext *context, in launched() function
360 g_signal_connect (context, "launched", G_CALLBACK (launched), NULL); in test_launch_context_signals()
|
| /third_party/skia/third_party/externals/oboe/apps/OboeTester/docs/ |
| D | AutomatedTesting.md | 6 It can be launched from a shell script by using an Android Intent.
8 Before running the app from an Intent, it should be launched manually and a Round Trip Latency test…
|
| /third_party/flutter/engine/flutter/frontend_server/ |
| D | README.md | 31 Relative paths should be relative to current working directory for the shell that launched
|
| /third_party/boost/tools/build/doc/src/ |
| D | debug.adoc | 30 is launched.
|
| /third_party/glib/gio/ |
| D | gappinfo.h | 293 void (* launched) (GAppLaunchContext *context, member
|
| /third_party/skia/third_party/externals/angle2/doc/ |
| D | DevSetupAndroid.md | 81 apps must be launched by the Java runtime since the libraries are discovered within an installed
109 Remember that ANGLE can only be used by applications launched by the Java runtime.
|
| /third_party/libuv/docs/src/guide/ |
| D | processes.rst | 68 Before the child process is launched you can control the execution environment
371 Turning now to the master, let's take a look at how the workers are launched to
395 straightforward till here. The workers are launched and waiting for file
|
| /third_party/boost/libs/outcome/doc/src/content/motivation/ |
| D | narrow_contract.md | 95 * a debugger can be launched,
|
| /third_party/flutter/flutter/examples/flutter_gallery/test_driver/ |
| D | transitions_perf_test.dart | 219 // 'Start Transition' event when a demo is launched (see GalleryItem).
|
| /third_party/flutter/flutter/packages/flutter_tools/lib/src/commands/ |
| D | daemon.dart | 1088 /// The method by which the flutter app was launched.
1092 /// The app was launched via `flutter run`.
1095 /// The app was launched via `flutter attach`.
|
12345