Skip to content

[BUG] - Issue Title 服务升级契约加载导致内存泄露 #5061

Open

Description

@mike-huawei

Steps to Reproduce

1、服务B升级
2、服务A调用服务B,A的内存占用增加(永远不会释放)

Expected Behavior

有定期清理机制

Servicecomb Version

2.8.24

Additional Context

怀疑是这里的问题:

Image

Activity

  1. chengyouling commented on Jan 20, 2026

    @chengyouling
    Contributor

    应该不会是这里的问题,可以观察下是不是一直打印load schema from service center......相关日志

  2. chengyouling commented on Jan 20, 2026

    @chengyouling
    Contributor

    上游服务A长时间不重启,下游服务B频繁变更升级,导致A不停加载B服务契约,导致内存消耗增加。

  3. added 3 commits that reference this issue on Jan 24, 2026
  4. hezhangjian commented on Nov 13, 2026

    @hezhangjian
    Member

    Following up on the memory-growth report on 2.8.24.

    #5062 (against 2.8.x) and #5064 (against 2.9.x) were opened for this issue, then closed on 6 March 2026 without being merged, and their head branches were deleted. I compared SwaggerLoader.java in 2.8.24 with the later published 2.8.31 and 2.9.5 releases; the file content is the same, so I do not see this change in a published release.

    On #5064 there was also an open question about whether the proposed cache-key change would actually address leaks caused by frequent version upgrades. I have not verified a root cause or a working fix.

    Could you confirm whether you can still reproduce this on a later published 2.8.x or 2.9.x release, and share sanitized memory / load schema from service center observations if you can? That will help us decide the next investigation step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions