Bug 23694 - Application crashes on screenshot capture
Summary: Application crashes on screenshot capture
Status: RESOLVED UPSTREAM
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.18.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-10-08 17:06 UTC by Mohan
Modified: 2014-10-13 10:06 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Android Device Settings Page (145.87 KB, image/png)
2014-10-08 17:06 UTC, Mohan
Details
Logcat (525.56 KB, text/plain)
2014-10-08 17:07 UTC, Mohan
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED UPSTREAM

Description Mohan 2014-10-08 17:06:34 UTC
Created attachment 8359 [details]
Android Device Settings Page

Steps to reproduce :
1. Create a Xamarin Android WebApplication 
2. Choose Target as 4.4 in settings , minSDK in manifest.xml as 4.4.2(equivalent API version)
3. Generate the Signed apk and deploy on the device.
4. Invoke the application 
5. Capture screenshot through swiping palm from right to left on a Samsung Galaxy S5 ( Android version 4.4.4, verizon build)
6. Application gets crashed

This issue is not reproducible in Android 4.4.2 .
Please refer to the attachments for more details


I/AudioPlayer(  386): First fillBuffer call!!
D/SpenGestureManagerService(  828): getSmartClipDataFromCurrentScreen()
D/SpenGestureManagerService(  828): checkPermission : Have permission
D/SmartClipDataCropperImpl(14499): doExtractSmartClipData : Extraction start! re
qId = -1  Cropped area = Rect(0, 0 - 1080, 1920)  Package = com.halliburton.corp
.insitemobile
W/WebView (14499): extractSmartClipData is called
D/SmartClipDataCropperImpl(14499): getOpaqueBackgroundRect : opaqueRect=null  el
ement=com.samsung.android.smartclip.SmartClipDataElementImpl@42618420
D/SmartClipDataCropperImpl(14499): getOpaqueBackgroundRect : opaqueRect=null  el
ement=com.samsung.android.smartclip.SmartClipDataElementImpl@42618068
D/SmartClipDataCropperImpl(14499): addAppMetaTag : package name is com.halliburt
on.corp.insitemobile
D/WindowManager(  828): called dispatchSmartClipDataExtractionEvent()
E/mono-rt (14499):
E/mono-rt (14499): =============================================================
====
E/mono-rt (14499): Got a SIGSEGV while executing native code. This usually indic
ates
E/mono-rt (14499): a fatal error in the mono runtime or one of the native librar
ies
E/mono-rt (14499): used by your application.
E/mono-rt (14499): =============================================================
====
E/mono-rt (14499):
F/libc    (14499): Fatal signal 11 (SIGSEGV) at 0x000002dc (code=1), thread 1454
2 (Chrome_InProcRe)
I/OMXCodec(  386): [OMX.google.vorbis.decoder] End Of Stream
V/AwesomePlayer(  386): postAudioEOS delayUs (0)
V/AwesomePlayer(  386): onCheckAudioStatus
V/AwesomePlayer(  386): onCheckAudioStatus() set AUDIO_AT_EOS flag
V/AwesomePlayer(  386): onStreamDone
Comment 1 Mohan 2014-10-08 17:07:45 UTC
Created attachment 8360 [details]
Logcat
Comment 2 Jonathan Pryor 2014-10-13 10:06:55 UTC
Thank you for the logcat. (Question: Why is it line-wrapped?!)

Which Xamarin.Android version is this with? If it's 4.18, I would expect to see debuggerd output around the site of the SIGSEGV, often along with a (partial) native callstack and possibly a Java stack trace; neither are present.

The fact that it works on 4.4.2 and fails on 4.4.4 suggests that this is an Android bug, not a Xamarin.Android bug. For example:

https://github.com/driftyco/ionic/issues/2350