Bug 13111 - xFinium PDF Library fails when used with Asyn/Await features
Summary: xFinium PDF Library fails when used with Asyn/Await features
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.7.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-07-09 01:34 UTC by Prashant Cholachagudda
Modified: 2014-07-28 17:04 UTC (History)
3 users (show)

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

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 INVALID

Description Prashant Cholachagudda 2013-07-09 01:34:32 UTC
xFinium PDF Library fails with below exception when used with Asyn/Await features (https://components.xamarin.com/view/XFINIUM.PDF)

Object reference not set to an instance of an object
at .. (System.IO.Stream , System.Double[] , Int32 , Int32 ) [0x00000] in <filename unknown>:0
at .. (System.IO.Stream , System.Double[] ) [0x00000] in <filename unknown>:0
at .. (System.IO.Stream , Double , Double , Double , Double , Int32 ) [0x00000] in <filename unknown>:0
at Xfinium.Pdf.Graphics.PdfFormXObject..ctor (Double width, Double height) [0x00000] in <filename unknown>:0
at Xfinium.Pdf.Annotations.PdfAnnotationAppearance..ctor (Double width, Double height) [0x00000] in <filename unknown>:0
at Xfinium.Pdf.Forms.PdfTextBoxWidget. () [0x00000] in <filename unknown>:0
at Xfinium.Pdf.Forms.PdfTextBoxField.SetFieldValue (System.Object value) [0x00000] in <filename unknown>:0
at Xfinium.Pdf.Forms.PdfTextBoxField.set_Text (System.String value) [0x00000] in <filename unknown>:0
at NullProblemInStream.Activity1+<>c__DisplayClass16.<OnPdfClick>b__d () [0x00019] in c:\\Users\\oansquer\\Documents\\Visual Studio 2012\\Projects\
ullProblemInStream\
ullProblemInStream\\Activity1.cs:109
at System.Threading.Tasks.TaskActionInvoker+ActionInvoke.Invoke (System.Threading.Tasks.Task owner, System.Object state, System.Threading.Tasks.Task context) [0x00000] in <filename unknown>:0
at System.Threading.Tasks.Task.InnerInvoke () [0x00000] in <filename unknown>:0
at System.Threading.Tasks.Task.ThreadStart () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at NullProblemInStream.Activity1+<OnPdfClick>d__18.MoveNext () [0x0025c] in c:\\Users\\oansquer\\Documents\\Visual Studio 2012\\Projects\
ullProblemInStream\
ullProblemInStream\\Activity1.cs:105
Comment 2 Atsushi Eno 2013-07-09 04:00:27 UTC
If that's about async/await, I have no idea what causes that. We likely need to get our runtime/compiler guys involved.
Comment 3 Marek Safar 2013-07-09 04:17:46 UTC
Based on the stack the source code was compiled using csc, so nothing there for me. But it's possible that it's a runtime bug. The library is obfuscated and there is chance that our runtime cannot deal with this type of obfuscation.
Comment 4 Atsushi Eno 2014-02-05 09:29:59 UTC
Not sure why it is categorized as binding. It is about async/await and/or runtime.
Comment 5 Jonathan Pryor 2014-07-28 17:04:55 UTC
As per Comment #3, we cannot investigate a runtime failure when the app has been obfuscated (is it an app bug? an obfuscated classlib bug? a bug with mono not handling obfuscated IL?).

Please provide a test case which doesn't involve obfuscated code.