Opened 2 years ago

Closed 2 years ago

#2595 closed defect (fixed)

ANR: executing service

Reported by: Meeh Owned by: zzz
Priority: minor Milestone: 0.9.43
Component: apps/android Version: 0.9.41
Keywords: Cc: zzz, idk
Parent Tickets: Sensitive: no


"main" prio=5 tid=1 Native
  | group="main" sCount=1 dsCount=0 obj=0x73ba8e40 self=0xb840f290
  | sysTid=27002 nice=0 cgrp=default sched=0/0 handle=0xb6efbc00
  | state=D schedstat=( 0 0 0 ) utm=91 stm=75 core=3 HZ=100
  | stack=0xbe2be000-0xbe2c0000 stackSize=8MB
  | held mutexes=
  at (Native method)
  at (
  at (
  at (
  at (
  at$ (
- locked <0x06ea77b8> (a java.lang.Object)
  at (
  at (
  at$EditorImpl.commit (
  at (
  at (
  at (
- locked <0x029f3991> (a java.lang.Object)
  at (
  at (
  at$H.handleMessage (
  at android.os.Handler.dispatchMessage (
  at android.os.Looper.loop (
  at (
  at java.lang.reflect.Method.invoke! (Native method)
  at$ (
  at (


#2632: ANR: executing service

Change History (4)

comment:1 Changed 2 years ago by zzz

The fix would be to thread the state saving to get the I/O out of the UI thread. We have a similar dilemma over in i2ptunnel, where we're unsure whether to wait at all, wait for a while, or wait forever… and how to ensure consistency.

comment:2 Changed 2 years ago by zzz

Milestone: undecided0.9.43
Owner: changed from Meeh to zzz
Status: newaccepted

comment:3 Changed 2 years ago by zzz

Add a subticket #2632 (ANR: executing service

comment:4 Changed 2 years ago by zzz

Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.