| /external/libchrome/base/message_loop/ |
| message_loop.cc | 147 // DCHECK(loop) << "Ouch, did you forget to initialize me?";
|
| /external/mockito/src/main/java/org/mockito/internal/util/reflection/ |
| GenericMetadataSupport.java | 263 throw new MockitoException("Ouch, it shouldn't happen, type '" + type.getClass().getCanonicalName() + "' on method : '" + method.toGenericString() + "' is not supported : " + type);
|
| /external/mp4parser/isoparser/src/main/java/com/googlecode/mp4parser/authoring/builder/ |
| DefaultMp4Builder.java | 100 // ouch that is ugly but I don't know how to do it else
|
| /external/python/cpython2/Python/ |
| codecs.c | 647 /* ouch: passing NULL, 0, pos gives None instead of u'' */
|
| /external/python/cpython3/Lib/test/ |
| test_capi.py | 608 r" at tail\+0: 0x78 \*\*\* OUCH\n"
|
| /external/valgrind/coregrind/m_debuginfo/ |
| priv_d3basics.h | 566 DW_OP_HP_unknown = 0xe0, /* Ouch, the same as GNU_push_tls_address. */
|
| /toolchain/binutils/binutils-2.27/include/ |
| dwarf2.def | 623 DW_OP_DUP (DW_OP_HP_unknown, 0xe0) /* Ouch, the same as GNU_push_tls_address. */
|
| /tools/tradefederation/core/tests/src/com/android/tradefed/testtype/suite/ |
| ModuleDefinitionTest.java | 291 final String exceptionMessage = "ouch I failed";
[all...] |
| /external/apache-xml/src/main/java/org/apache/xml/dtm/ref/ |
| DTMManagerDefault.java | 517 // already examined. Ouch. But with the increased number of DTMs,
|
| /external/apache-xml/src/main/java/org/apache/xml/serializer/ |
| SerializerBase.java | [all...] |
| /external/pdfium/third_party/lcms/src/ |
| cmsps2.c | [all...] |
| /toolchain/binutils/binutils-2.27/bfd/ |
| bout.c | 854 /* Ouch! this reloc is out of order, insert into the right place. */
[all...] |
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.10/Objects/ |
| obmalloc.c | [all...] |
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Objects/ |
| obmalloc.c | [all...] |
| /external/antlr/antlr-3.4/tool/src/test/java/org/antlr/test/ |
| TestAttributes.java | [all...] |
| /external/python/cpython2/Objects/ |
| obmalloc.c | [all...] |
| /external/python/cpython3/Objects/ |
| obmalloc.c | [all...] |
| /external/curl/src/ |
| tool_operate.c | 823 /* Ouch, there's already a question mark in the URL string, we
[all...] |
| /external/icu/android_icu4j/src/main/java/android/icu/impl/ |
| ICUResourceBundle.java | 638 if (DEBUG) System.out.println("ouch: " + e.getMessage());
[all...] |
| /external/icu/icu4j/main/classes/core/src/com/ibm/icu/impl/ |
| ICUResourceBundle.java | 634 if (DEBUG) System.out.println("ouch: " + e.getMessage());
[all...] |
| /frameworks/base/services/usb/java/com/android/server/usb/ |
| UsbDeviceManager.java | [all...] |
| /external/ImageMagick/ImageMagick/script/ |
| architecture.html | 252 <p>Recall that this simple and elegant design of the ImageMagick pixel cache comes at a cost in terms of storage and processing speed. The pixel cache storage requirements scales with the area of the image and the bit depth of the pixel components. For example, if we have a 640 by 480 image and we are using the Q16 version of ImageMagick, the pixel cache consumes image <var>width * height * bit-depth / 8 * channels</var> bytes or approximately 2.3 mebibytes (i.e. 640 * 480 * 2 * 4). Not too bad, but what if your image is 25000 by 25000 pixels? The pixel cache requires approximately 4.7 gibibytes of storage. Ouch. ImageMagick accounts for possible huge storage requirements by caching large images to disk rather than memory. Typically the pixel cache is stored in memory using heap memory. If heap memory is exhausted, pixels are stored in in an anonymous map; if the anonymous memory map is exhausted, we create the pixel cache on disk and attempt to memory-map it; and if memory-map memory is exhausted, we simply use standard disk I/O. Disk storage is cheap but it is also very slow, upwards of 1000 times slower than memory. We can get some speed improvements, up to 5 times, if we use memory mapping to the disk-based cache. These decisions about storage are made <var>automagically</var> by the pixel cache manager negotiating with the operating system. However, you can influence how the pixel cache manager allocates the pixel cache with <var>cache resource limits</var>. The limits include:</p>
[all...] |
| /external/ImageMagick/www/ |
| architecture.html | 256 <p>Recall that this simple and elegant design of the ImageMagick pixel cache comes at a cost in terms of storage and processing speed. The pixel cache storage requirements scales with the area of the image and the bit depth of the pixel components. For example, if we have a 640 by 480 image and we are using the Q16 version of ImageMagick, the pixel cache consumes image <var>width * height * bit-depth / 8 * channels</var> bytes or approximately 2.3 mebibytes (i.e. 640 * 480 * 2 * 4). Not too bad, but what if your image is 25000 by 25000 pixels? The pixel cache requires approximately 4.7 gibibytes of storage. Ouch. ImageMagick accounts for possible huge storage requirements by caching large images to disk rather than memory. Typically the pixel cache is stored in memory using heap memory. If heap memory is exhausted, we create the pixel cache on disk and attempt to memory-map it. If memory-map memory is exhausted, we simply use standard disk I/O. Disk storage is cheap but it is also very slow, upwards of 1000 times slower than memory. We can get some speed improvements, up to 5 times, if we use memory mapping to the disk-based cache. These decisions about storage are made <var>automagically</var> by the pixel cache manager negotiating with the operating system. However, you can influence how the pixel cache manager allocates the pixel cache with <var>cache resource limits</var>. The limits include:</p>
[all...] |
| /external/harfbuzz_ng/ |
| NEWS | 689 - Another hb-coretext crasher fix. Ouch!
[all...] |
| /external/valgrind/memcheck/ |
| mc_leakcheck.c | 712 VG_(printf)("OUCH! sig=%d addr=%#lx who=%s\n", sigNo, addr, who);
[all...] |
