TeamAmaze / TeamAmaze/AmazeFileManager

saving text file crashed

Open
#2,402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-TextEditor From-Email Issue-Bug
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Issue explanation (write below this line)

Was typing in a text file opened from drop box. Had saved it a few mins
before, written 50 or so words since save before it crashed.

Exception

  • User Action: UI Error
  • Request: Application crash
  • Version: 3.5.3
  • OS: Linux
    Nokia/DoctorDoom_00EEA/DRD_sprout:10/QKQ1.200719.002/00WW_1_160:user/release-keys
    10 - 29
  • Device: DRD_sprout
  • Model: Nokia 5.4
  • Product: DoctorDoom_00EEA
Crash log

java.lang.ArrayIndexOutOfBoundsException: src.length=38906 srcPos=20388
dst.length=19044 dstPos=525 length=18519
at java.lang.System.arraycopy(Native Method)
at
android.text.SpannableStringBuilder.getChars(SpannableStringBuilder.java:1213)
at
android.text.SpannableStringBuilder.toString(SpannableStringBuilder.java:1227)
at
com.amaze.filemanager.ui.activities.TextEditorActivity$1.run(TextEditorActivity.java:432)
at java.util.TimerThread.mainLoop(Timer.java:562)
at java.util.TimerThread.run(Timer.java:512)


Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at TextEditorActivity.java line 432, where the crash log shows the text editor's save-related work failing during SpannableStringBuilder.toString(). Reproduce saving a text file after editing, then verify the crash no longer occurs and that the edited text is preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.