Re: Android: crash on deleting dives

2017-07-04 Thread Willem Ferguson 
>From phone. I reliably get a crash when using the red button for delete.
Deleting from details (profile) view appears to delete dives reliably.
Kind regards,
Willem

On 04 Jul 2017 4:43 PM, "Dirk Hohndel"  wrote:

>
> > On Jul 4, 2017, at 12:18 AM, Rick Walsh  wrote:
> >
> > Hi,
> >
> > Testing the latest daily Subsurface-mobile Android build, 4.6.4.333, I
> get a crash sometimes when deleting a dive.  It may be a coincidence, but
> it only appears to crash when deleting a dive that is not the most recent.
> Below is the output from 'adb logcat | grep -i subsurface', where I opened
> Subsurface-mobile and successfully deleted some dives, before crashing on
> the fourth or fifth.  I first noticed this problem a week or so ago, so
> this does not appear to be caused by one of the most recent changes.
>
> We've seen this on and off and if I was able to reproduce it reliably I'd
> love to fix it... really.
>
> I just spent about ten minutes on my phone with test data, randomly
> deleting dives, undo-ing the deletes, doing more deletes. Can't make it
> crash.
>
> Quick question: do you use the delete on the action button in the dive
> details view, or do you use the tap-and-hold delete from the dive list?
>
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android: crash on deleting dives

2017-07-04 Thread Dirk Hohndel 

> On Jul 4, 2017, at 12:18 AM, Rick Walsh  wrote:
> 
> Hi,
> 
> Testing the latest daily Subsurface-mobile Android build, 4.6.4.333, I get a 
> crash sometimes when deleting a dive.  It may be a coincidence, but it only 
> appears to crash when deleting a dive that is not the most recent.  Below is 
> the output from 'adb logcat | grep -i subsurface', where I opened 
> Subsurface-mobile and successfully deleted some dives, before crashing on the 
> fourth or fifth.  I first noticed this problem a week or so ago, so this does 
> not appear to be caused by one of the most recent changes.

We've seen this on and off and if I was able to reproduce it reliably I'd love 
to fix it... really.

I just spent about ten minutes on my phone with test data, randomly deleting 
dives, undo-ing the deletes, doing more deletes. Can't make it crash.

Quick question: do you use the delete on the action button in the dive details 
view, or do you use the tap-and-hold delete from the dive list?

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Android: crash on deleting dives

2017-07-04 Thread Rick Walsh 
Hi,

Testing the latest daily Subsurface-mobile Android build, 4.6.4.333, I get
a crash sometimes when deleting a dive.  It may be a coincidence, but it
only appears to crash when deleting a dive that is not the most recent.
Below is the output from 'adb logcat | grep -i subsurface', where I opened
Subsurface-mobile and successfully deleted some dives, before crashing on
the fourth or fifth.  I first noticed this problem a week or so ago, so
this does not appear to be caused by one of the most recent changes.

07-04 19:03:23.319  4980  5777 I ActivityManager: START u0
{act=android.intent.action.MAIN typ=null flg=0x1020
cmp=ComponentInfo{org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity}}
from uid 10064 on display 0
07-04 19:03:23.327  4980  5777 D ActivityManager: computeStackFocus: New
stack r=ActivityRecord{99aa06ed0 u0
org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity
t-1} stackId=1
07-04 19:03:23.327  4980  5777 I MultiWindowManagerService:
setTaskDimensions: Task=TaskRecord{5d4557ad0 #4314
A=org.subsurfacedivelog.mobile U=0 StackId=1 sz=1} minWidth=-1 minHeight=-1
maxWidth=-1 maxHeight=-1
07-04 19:03:23.328  4980  5777 D ActivityManager: moveToFront() :
reason=startedActivity setFocusedActivity isAttached=true
TaskRecord{5d4557ad0 #4314 A=org.subsurfacedivelog.mobile U=0 StackId=1
sz=1}
07-04 19:03:23.329  4980  5777 D ActivityManager:
resumeTopActivityInnerLocked() : #1 prevTask=TaskRecord{5d4557ad0 #4314
A=org.subsurfacedivelog.mobile U=0 StackId=1 sz=1}
next=ActivityRecord{99aa06ed0 u0
org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity
t4314} mFocusedStack=ActivityStack{885a8c1d0 stackId=1, 22 tasks}
07-04 19:03:23.337  4980  5073 D ActivityManager:
resumeTopActivityInnerLocked() : #1 prevTask=TaskRecord{edc3b6cd0 #4204
A=com.sec.android.app.launcher U=0 StackId=0 sz=1}
next=ActivityRecord{99aa06ed0 u0
org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity
t4314} mFocusedStack=ActivityStack{885a8c1d0 stackId=1, 22 tasks}
07-04 19:03:23.338  4980  5073 D MountService: getExternalStorageMountMode
: final mountMode=3, uid : 10233, packageName : org.subsurfacedivelog.mobile
07-04 19:03:23.352  4980  5073 I ActivityManager: Start proc
306:org.subsurfacedivelog.mobile/u0a233 for activity
org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity
07-04 19:03:23.357   306   306 I SELinux : SELinux: seapp_context_lookup:
seinfo=untrusted, level=s0:c512,c768, pkgname=org.subsurfacedivelog.mobile
07-04 19:03:23.378  4980  5778 I ActivityManager: DSS on for
org.subsurfacedivelog.mobile and scale is 1.0
07-04 19:03:23.379  4980  5116 V WindowManager: Relayout Window{9aaa159d0
u0 Starting org.subsurfacedivelog.mobile}: viewVisibility=0 req=1080x1848
WM.LayoutParams{(0,0)(fillxfill) sim=#20 ty=3 fl=#1830118 pfl=0x11 fmt=-3
wanim=0x103038a needsMenuKey=2 naviIconColor=0}
07-04 19:03:23.401  4980  4980 D GameManagerService: NotifyRunnable. pkg:
org.subsurfacedivelog.mobile, type: 4, isMinimized: false, isTunableApp:
false
07-04 19:03:23.405  4980  7703 D GameManagerService: identifyGamePackage.
org.subsurfacedivelog.mobile
07-04 19:03:23.407  4980  5116 D WindowManager: finishDrawingWindow:
Window{9aaa159d0 u0 Starting org.subsurfacedivelog.mobile}
mDrawState=DRAW_PENDING
07-04 19:03:23.407  4980  7703 D GameManagerService: identifyGamePackage.
org.subsurfacedivelog.mobile
07-04 19:03:23.412  4980  5116 D WindowManager: finishDrawingWindow:
Window{9aaa159d0 u0 Starting org.subsurfacedivelog.mobile}
mDrawState=HAS_DRAWN
07-04 19:03:23.417  4980  7703 D GameManagerService: identifyGamePackage.
org.subsurfacedivelog.mobile
07-04 19:03:23.417  4980  7703 D GameManagerService: identifyGamePackage.
org.subsurfacedivelog.mobile
07-04 19:03:23.534  4980  5406 D MdnieScenarioControlService:  packageName
: org.subsurfacedivelog.mobileclassName :
org.qtproject.qt5.android.bindings.QtActivity
07-04 19:03:23.536   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Concurrent.so:
unsupported flags DT_FLAGS_1=0x81
07-04 19:03:23.539   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Gui.so: unsupported
flags DT_FLAGS_1=0x81
07-04 19:03:23.549   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Widgets.so:
unsupported flags DT_FLAGS_1=0x81
07-04 19:03:23.563   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Svg.so: unsupported
flags DT_FLAGS_1=0x81
07-04 19:03:23.566   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Positioning.so:
unsupported flags DT_FLAGS_1=0x81
07-04 19:03:23.569   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Network.so:
unsupported flags DT_FLAGS_1=0x81
07-04 19:03:23.574   306   306 W linker  :
/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libQt5Qml.so: unsupported
flags DT_FLAGS_1=0x81
07-04 19:03:23.588   306   306 W li