try {
                        ((Destroyable) masterKey).destroy();
                    } catch (DestroyFailedException e) {
                        // Log but continue - not all JVM implementations support destroying SecretKey
                        log.debug("SecretKey destroy not fully supported: {}", e.getMessage());
                        failedToDestroy = true;

        try {
            storage.destroy();
        } catch (DestroyFailedException e) {
            // This is acceptable - not all JVM implementations support destroying SecretKey
            // The important part is that the storage is marked as destroyed
        }

        assertTrue(storage.isDestroyed(), "Storage should be marked as destroyed");

   * intentionally, so there is no other way to clean up these threads. (The better solution,
   * though, would be to run the tests that use TestThread in separate VMs so that their threads
   * don't hang around during other tests.)
   */
  @Override
  public void tearDown() throws Exception {
    try {
      Thread.class.getMethod("stop").invoke(this);
      join();

        expect:
        (line =~ KillLeakingJavaProcesses.generateAllGradleProcessPattern()).find()
    }

    def "not matches TC agent JVM"() {

            // with a single version of the class in `jarExpandDir`.
            // This will be the closes version to `targetCompatibility`, the same class that would be loaded in a JVM
            // that has `targetCompatibility` version.
            // This means we only scan classes that would be loaded into `targetCompatibility`, and don't look at any

app.extension.names=

# Audit log format.
app.audit.log.format=

# Script audit log settings.
script.audit.log.enabled=true
script.audit.log.max.length=100

# JVM options for the crawler process.
jvm.crawler.options=\
-Djava.awt.headless=true\n\
-Dfile.encoding=UTF-8\n\
-Djna.nosys=true\n\
-Djdk.io.permissionsUseCanonicalPath=true\n\
-Dhttp.maxConnections=20\n\

        // Test with VirtualMachineError
        String url = "http://example.com/vm-error";
        String message = "VM error during crawling";
        InternalError error = new InternalError("JVM internal error");

        DataStoreCrawlingException exception = new DataStoreCrawlingException(url, message, error);

        assertEquals(url, exception.getUrl());

            }
        }
        long arrayDuration = System.nanoTime() - arrayStartTime;

        // Set-based lookup should be significantly faster
        // Note: This is a rough check - exact performance depends on JVM, hardware, etc.
        // We expect Set lookup to be at least as fast as array lookup for large datasets
        assertTrue("Set-based lookup should be faster or comparable to array-based lookup for large datasets",

#### Import Gradle into IntelliJ

To import Gradle into IntelliJ:
- Open the `build.gradle.kts` file in root of the project with IntelliJ and choose "Open as Project"
- Select a Adoptium Java 17 VM as "Gradle JVM"
- Revert the Git changes to files in the `.idea` folder

NOTE: Due to the project size, the very first import can take a while and IntelliJ might become unresponsive for several seconds during this period.

        }

        try {
          int offset = theUnsafe.arrayBaseOffset(byte[].class);
          int scale = theUnsafe.arrayIndexScale(byte[].class);

          // Use Unsafe only if we're in a 64-bit JVM with an 8-byte aligned field offset.
          if (Objects.equals(System.getProperty("sun.arch.data.model"), "64")
              && (offset % 8) == 0
              // sanity check - this should never fail