Databases
StackOverflow2013
Postsdbo
POIsolating unmanaged crashes under Mono
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIsolating unmanaged crashes under Mono
    primarykey
    data
    text
    <p>We have a Mono application under Linux that does image processing on a bunch of files.</p> <p>For this we (among other things) use System.Drawing, and for the most part it serves us well. Occasionally however, we encounter an image that crashes the application - it is a crash in a native call, and this is immune to try catch. Simplified, a call like</p> <pre><code>System.Drawing.Image.FromFile(imagePath); </code></pre> <p>will cause a crash. The error message looks something like this:</p> <pre><code>at (wrapper managed-to-native) System.Drawing.GDIPlus.GdipLoadImageFromFile (string,intptr&amp;) &lt;0xffffffff&gt; </code></pre> <p>This pulls the whole application down instantly.</p> <p>We have encountered a few instances that this happens - corrupt GIF files, unexpected headers in TIFF files - to name a few. As we don't have control over the source of the images, we will just have to deal with possible crashes.</p> <p><strong>The question:</strong> I would like to isolate the places where we use GDI+ (through System.Drawing) on untrusted files so that it can happily crash without killing the whole application. </p> <p>I have attempted this through using separate application domains, but I just can't stop the crashes. It is probable that I am doing it wrong!</p> <p><sub> Some detail: openSUSE 11.4 (x86_64), Mono version 2.10.2, libgdiplus0 (package) 2.10-30.2, libtiff3 (package) 3.9.4-3.7.1 </sub></p> <hr> <p>Please note that the specific issues we experienced was promptly fixed - see comments below. The question still remains though. </p> <p>I would have liked to somehow isolate a part of the program so that it does not pull the whole thing down - but I fear the only answer is to call a external process as noted in the answer below. I'll leave this as is for a while and then accept that answer!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFPC
    1. USFPC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIsolating unmanaged crashes under Mono
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIsolating unmanaged crashes under Mono
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIsolating unmanaged crashes under Mono
      1. USTheNextman
      1. VTFavorite
    1. COI would suggest filing bugs for the images that cause crashes (http://bugzilla.xamarin.com) so that the issues can be fixed. Since image parsing has historically been a source for security issues it would also be preferrable if you made the bug private to Xamarin so that you don't disclose a possible security issue.
      singulars
      1. POIsolating unmanaged crashes under Mono
      1. USRolf Bjarne Kvinge
    2. CORight, logged as http://bugzilla.xamarin.com/show_bug.cgi?id=1752 and http://bugzilla.xamarin.com/show_bug.cgi?id=1753 In the end we sidestepped System.Drawing when we can and rely on Gdk under Mono, which thus far seem much more robust.
      singulars
      1. POIsolating unmanaged crashes under Mono
      1. USFPC
    3. CO@FPC both issues are now fixed. Thanks!
      singulars
      1. POIsolating unmanaged crashes under Mono
      1. USpoupou
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload