TeamAmaze / TeamAmaze/AmazeFileManager

Crash on dialog when trying to delete 16000 files

Open
#2,698 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Press "delete" witg 16000 files selected, the list is unscrollable, and the activity crashes:

-------------------------------------
android.view.WindowManager$BadTokenException: Unable to add window -- token android.os.BinderProxy@2b08861 is not valid; is your activity running?
 at android.view.ViewRootImpl.setView(ViewRootImpl.java:748)
 at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:343)
 at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:94)
 at android.widget.Toast$TN.handleShow(Toast.java:504)
 at android.widget.Toast$TN$2.handleMessage(Toast.java:384)
 at android.os.Handler.dispatchMessage(Handler.java:102)
 at android.os.Looper.loop(Looper.java:154)
 at android.app.ActivityThread.main(ActivityThread.java:6351)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:896)
 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:786)
-------------------------------------

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 by reproducing deletion with about 16,000 selected files and trace the Android stack trace through the delete dialog and Toast handling. Done means the selected-file list remains usable and the activity does not crash when the deletion dialog is opened.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.