Stack overflow during NPC-portal loading screens

未关闭
#3,684 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
frontend, game-dev

调研方向

Start from follow-up #3426, then reproduce an NPC-portal loading screen with pause-on-exceptions enabled. Inspect the .push( ...array ) spreads in runtime/renderer/characters/characters.ts at lines 1156, 1686, 2466, 2886 and 3147, and verify whether any array exceeds V8's argument limit or whether another function is recursing. Done means the recursing function is identified, the root cause is confirmed, and a tested fix is in place.

由索引模型根据 Issue 内容生成。

描述

area: client bug priority: high

Follow-up from #3426

The actual cause of the "Maximum call stack size exceeded" errors during NPC-portal loading screens is not yet identified. Candidates (unverified): the .push( ...array ) spreads in runtime/renderer/characters/characters.ts (lines 1156, 1686, 2466, 2886, 3147). A spread past V8's argument limit (~120k) throws exactly this RangeError.

Done when

  • The recursing function is identified via pause-on-exceptions during NPC teleport loading
  • Root cause is confirmed (spread overflow vs other recursion)
  • Fix is implemented and tested
主要语言
Go
星标
97
派生
61
平均合并
4 小时 14 分钟
30 天内合并 PR
913

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

opensro-dev/opensro 的其他 Issue

查看 opensro-dev/opensro 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。