apache / apache/arrow-java

[Java][FlightRPC] TestBasicOperation.getStreamLargeBatch is flaky on Windows CI

未關閉
#236 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
Type: bug
主要語言
Java
星號
94
分支
152
平均合併
3 天 16 小時
30 天內合併 PR
11

描述

```

java.lang.IllegalStateException:
Memory was leaked by query. Memory leaked: (134217728)
Allocator(ROOT) 0/134217728/270532608/9223372036854775807 (res/actual/peak/limit)

at org.apache.arrow.memory.BaseAllocator.close(BaseAllocator.java:437)
at org.apache.arrow.memory.RootAllocator.close(RootAllocator.java:29)
at org.apache.arrow.flight.TestBasicOperation$Producer.close(TestBasicOperation.java:514)
at org.apache.arrow.flight.TestBasicOperation.test(TestBasicOperation.java:333)
at org.apache.arrow.flight.TestBasicOperation.test(TestBasicOperation.java:312)
at org.apache.arrow.flight.TestBasicOperation.getStreamLargeBatch(TestBasicOperation.java:270)
```

**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-18034) / @lidavidm
#### Related issues:
- [[Java] Enable allocator logging in CI](https://github.com/apache/arrow/issues/33238) (is related to)

**Note**: *This issue was originally created as [ARROW-18034](https://issues.apache.org/jira/browse/ARROW-18034). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*

貢獻指南

開啟貢獻指南

研究方向

從 TestBasicOperation.java 中的 getStreamLargeBatch 以及第 270-333 行附近的測試多載開始,接著檢查第 514 行附近的 Producer.close,以及 stack trace 回報的 allocator 洩漏。在 Windows CI 上重現此測試;完成條件是 getStreamLargeBatch 不再 flaky,且 allocator 關閉時不回報記憶體洩漏。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
java
領域
ci-cd, testing-qa
Issue 類型
缺陷
難度
3/5
預估耗時
1-2 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。