The recommended way to handle the *startup* and *shutdown* is using the `lifespan` parameter of the `FastAPI` app as described above. If you provide a `lifespan` parameter, `startup` and `shutdown` event handlers will no longer be called. It's all `lifespan` or all events, not both.

You can probably skip this part.

///

There's an alternative way to define this logic to be executed during *startup* and during *shutdown*.

                emergencyCleanup();
            }
        } catch (Exception e) {
            log.error("Error during tree finalization", e);
        } finally {
            super.finalize();
        }
    }

    /**
     * Emergency cleanup method to prevent memory leaks during finalization
     */
    private void emergencyCleanup() {
        try {
            // Force usage count to zero

     * @throws ChildUrlsException if child URLs are discovered during processing
     * @throws DataStoreCrawlingException if an error occurs during crawling
     */
    protected String processRequest(final DataStoreParams paramMap, final Map<String, Object> dataMap, final String url,
            final CrawlerClient client) {
        final SystemHelper systemHelper = ComponentUtil.getSystemHelper();

    /**
     * Converts the given content to an XML string.
     *
     * @param content the object to convert
     * @return the xml string representation
     * @throws XmlWriterException if an error occurs during the transformation
     * @see #fromXmlString(String)
     */
    @Nonnull
    default String toXmlString(@Nonnull T content) throws XmlWriterException {
        StringWriter sw = new StringWriter();
        write(content, sw);

/**
 * Interface for model transformers that can modify Maven project models at different stages of processing.
 * <p>
 * Model transformers allow plugins and extensions to modify the POM model during the build process.
 * Transformations can be applied at three different stages:
 * <ol>
 *   <li>File model - The raw model as read directly from the file</li>

     * @param to the end time in HH:MM format
     * @param days comma-separated list of days (1=Sunday, 7=Saturday)
     * @param delay the delay in milliseconds to apply during this interval
     */
    public void addIntervalRule(final String from, final String to, final String days, final long delay) {
        ruleList.add(new IntervalRule(from, to, days, delay));
    }

    /**
     * Checks if the crawler is currently running.

        int originalHexCode = 0xFF;
        mockName.hexCode = originalHexCode;

        // Create a spy to capture the state during writeQuestionSectionWireFormat
        NodeStatusRequest spyRequest = spy(nodeStatusRequest);
        doAnswer(invocation -> {
            // Verify hexCode is 0 during the call
            assertEquals(0x00, mockName.hexCode);
            return 40;

   */
  SipHashFunction(int c, int d, long k0, long k1) {
    checkArgument(
        c > 0, "The number of SipRound iterations (c=%s) during Compression must be positive.", c);
    checkArgument(
        d > 0, "The number of SipRound iterations (d=%s) during Finalization must be positive.", d);
    this.c = c;
    this.d = d;
    this.k0 = k0;
    this.k1 = k1;
  }

  @Override
  public int bits() {

    /**
     * Gets the NetBIOS name of the remote endpoint.
     * @return the name of the remote endpoint
     */
    String getNetbiosName();

    /**
     * Disposes of the security context and releases any associated resources.
     * @throws CIFSException if an error occurs during disposal
     */
    void dispose() throws CIFSException;

    /**
     * Checks whether the specified security mechanism is supported.

   on plugin goals execution order:

   * <<in a given phase, goals order is not expected to be guaranteed nor finely tuned>>:
     it is just a consequence of the order obtained during {{{../maven-model-builder/}effective model building}},
     which combines profile activation+injection and inheritance assembly from parents,

   * known limitations are notably that: