RSCs Server Side Memory Leak Issue

[LikeDreamwalker]

Summary

I am investigating a Next.js memory leak issue on the server side, and what now I have confirmed, that main reason of memory leak comes from the TLS Sockets, where I find that for the normal Sockets will be opened but removed finally on my server side, but not the TLS Sockets. And for the worst after running in 2 weeks, I got nearly over 3000+ TLS Sockets still open and bring my Next.js container uses over 5GB memory.

And now I am highly suspicious that I have done something wrong with the RSC and app router, but I can't figure out the specific code parts or reasons. All my routes works as expected but just still receiving this issue.

Additional information

I have exclude some possible reasons:
- Node.js bug (I was in the fixed version and update to the newest)
- Server Side fetch cache issue (Use Axios instead with proper settings, might related but not the main reason)
- Server Side http agents issue (Since I finally got the endless TLS Sockets, I think they might not related)

And I can share a normal RSC route I would code as often:

import CreateClient from "@/components/assets-client";
import { getAssetsList } from "@/actions/task-list";
import { getCookies } from "@/actions/cookies";
import TaskList from "@/components/task-list";
import { TaskList as TaskListType } from "@/lib/biz/types";
import MoreTaskList from "@/components/task-list/more-task-list";
import { TaskListProvider } from "@/components/task-list/context";
import { pageSize } from "@/lib/biz";
import FilterBar from "@/components/filter-bar";
import AssetsPagination from "@/components/task-list/assets-pagination";
import { getAssetsDirectory } from "@/actions/assets";
import { DirectoryItem } from "@/actions/assets/types";

export default async function Home(props: {
  params: Promise<{ locale: string }>;
  searchParams: Promise<{
    tab?: string;
    media?: string;
    taskType?: string;
    pageNum?: number;
  }>;
}) {
  const params = await props.params;
  const searchParams = await props.searchParams;

  const { locale } = params;

  const getFilterData = async () => {
    const res = await getAssetsDirectory({
      media: searchParams?.media || "all",
    } as { media: string });
    return res.code === "200" ? res.data : [];
  };

  const getAssetsInitData = async (): Promise<{
    taskListData: TaskListType;
    processingLength: number;
  }> => {
    const res = await getAssetsList({
      pageNum: searchParams.pageNum || 1,
      statusType: "processing",
      type: searchParams.tab || "creatives",
      taskType: searchParams.taskType,
      assetType: searchParams.media,
    });

    const processingResData = res.code === "200" ? res.data : [];
    return {
      taskListData: [...processingResData],
      processingLength: processingResData.length,
    };
  };

  const [filterData, { taskListData }] = await Promise.all([
    getFilterData(),
    getAssetsInitData(),
  ]);

  const defaultTab = filterData?.[0];
  const curTabKey = searchParams.tab || defaultTab?.key || "creatives";
  const curMediaKey =
    searchParams.media || defaultTab?.children?.[0]?.key || "all";

  const curPageNum = Number(searchParams.pageNum) || 1;

  return (
    <div className="w-full h-full min-h-[100vh] flex flex-col">
      <TaskListProvider>
        <FilterBar
          curTab={curTabKey}
          curTaskType={searchParams.taskType}
          curMediaType={curMediaKey}
          filterData={filterData}
        />
        {taskListData.length > 0 && (
          <TaskList taskListData={taskListData} pageNum={curPageNum} />
        )}
        <AssetsPagination
          curPageNum={curPageNum}
          curDataSize={taskListData.length}
          searchParams={searchParams}
        />
      </TaskListProvider>
      <CreateClient locale={locale} testData={taskListData} />
    </div>
  );
}

 
I know I probably not coding RSC as very official but I really can't see the critical issue that related with the endless TLS Sockets.

Hope someone have met this before or if there is a way to add some detection about RSCs status.

Example

No response

[LikeDreamwalker]

I have built up a monitor for my online site read only, so anyone who is interested in this, you can visit this site to read some basic info about this memory leak issue

[LikeDreamwalker]

Also to make a little clarify that my app will work with the real service in the same deploy machine, where they use the HTTP directly, so for the TLS Socket looks more like the connection between the client side with my server side using HTTPS proxy directly, still I think the best shot is the RSC Streaming or the Server Action.