zhanghai / zhanghai/MaterialFiles
[Bug] The FTP Server crashed.
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 9k
- Forks
- 736
- PR merge metrics
- No merged PRs in 30d
Description
Reproduction And Environment
The reproduction steps and environment are very similar to https://github.com/TeamAmaze/AmazeFileManager/issues/4398#issue-3049099201.
Trace
FATAL EXCEPTION: pool-5-thread-5 Process: me.zhanghai.android.files, PID: 11085 java.nio.charset.CoderMalfunctionError: java.lang.IllegalArgumentException: newPosition > limit: (33 > 31) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:624) at V6.a.x(SourceFile:29) at Q6.d.a(SourceFile:18) at e7.e.d(SourceFile:40) at X6.d.j(SourceFile:5) at X6.a.c(SourceFile:9) at X6.j.a(SourceFile:79) at i7.c.p(SourceFile:270) at k7.a.d(SourceFile:8) at X6.d.j(SourceFile:5) at X6.a.c(SourceFile:9) at X6.g.d(SourceFile:1) at X6.d.j(SourceFile:5) at X6.a.c(SourceFile:9) at X6.g.d(SourceFile:1) at X6.d.j(SourceFile:5) at b7.c.A(SourceFile:107) at N6.i.A(SourceFile:3) at G6.a.a(SourceFile:644) at Q6.b.e(SourceFile:175) at X6.c.f(SourceFile:105) at X6.d.c(SourceFile:5) at X6.a.e(SourceFile:9) at Q6.c.f(SourceFile:33) at X6.d.c(SourceFile:5) at X6.a.e(SourceFile:9) at X6.j.a(SourceFile:101) at i7.c.p(SourceFile:270) at k7.a.f(SourceFile:8) at X6.d.c(SourceFile:5) at X6.a.e(SourceFile:9) at e7.c.a(SourceFile:13) at e7.e.f(SourceFile:74) at X6.d.c(SourceFile:5) at X6.a.e(SourceFile:9) at X6.j.a(SourceFile:101) at b7.m.run(SourceFile:1) at g7.e.a(SourceFile:37) at g7.e.run(SourceFile:169) at java.lang.Thread.run(Thread.java:1012) Caused by: java.lang.IllegalArgumentException: newPosition > limit: (33 > 31) at java.nio.Buffer.createPositionException(Buffer.java:353) at java.nio.Buffer.position(Buffer.java:328) at java.nio.CharBuffer.position(CharBuffer.java:1651) at com.android.icu.charset.CharsetEncoderICU.setPosition(CharsetEncoderICU.java:251) at com.android.icu.charset.CharsetEncoderICU.encodeLoop(CharsetEncoderICU.java:189) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:622) ... 39 more
Configuration
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction issue and the FTP server path implicated by the CharsetEncoder trace. Reproduce the crash using the reported configuration, then trace the FTP server's charset-encoding flow; done means the server no longer crashes for that case and a regression test covers it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- mobile-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100