[Bug 52635] New: WarpEM fails to process data with: internal error in the .NET Runtime at IP 00000000014B7F8A (00000000013F0000) with exit code 80131506

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52635

Bug ID: 52635
           Summary: WarpEM fails to process data with:  internal error in
                    the .NET Runtime at IP 00000000014B7F8A
                    (00000000013F0000) with exit code 80131506
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 71960
  --> https://bugs.winehq.org/attachment.cgi?id=71960
Screenshot with settings in WarpEM GUI

Trying to do some data processing with WarpEM fails with this error:

0280:err:eventlog:ReportEventW L"Application: WarpWorker.exe\nFramework
Version: v4.0.30319\nDescription: The process was terminated due to an internal
error in the .NET Runtime at IP 00000000014B7F8A (00000000013F0000) with exit
code 80131506.\n"

In order to reproduce the issue, I did the following:

* install WarpEM 1.0.9 on wine-staging 7.3/Debian10 according to 
https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620

* Download about 50 data sets or more from 
  http://ftp.ebi.ac.uk/empiar/world_availability/10721/data/
  (the total set is 1.5TB with 2834 files, 50 are sufficient)

* Start WarpEM and set "Input: directory" to local copy of th data, and set
"Input: Extension" to "*.tiff".

* Adapt settings in WarpEM gui according to attached screenshot
  (Pixel X/Y: 0.4190/0.4190, Bin:1, Exposure 1, Range 20.0-2.8, Motion
33.5-6.7,  Motion Grid 6x4x70, etc.)

* Click on "START PROCESSING"

Then for each selected gpu, a WarpWorker (cmd) window is openend, which
eventually dies, and Wine reports for each work this error:

093c:err:eventlog:ReportEventW L"Application: WarpWorker.exe\nFramework
Version: v4.0.30319\nDescription: The process was terminated due to an internal
error in the .NET Runtime at IP 00000000014B7F8A (00000000013F0000) with exit
code 80131506.\n"

Once these WarpWorker Windows closed, pressing "STOP PROCESSING" has no effect,
and Warp can only be closed by closing the window, and stopping wine with
<Ctrl-C> .

I understand that the error code indicates a problem with memory management and
garbage collection, so it might be also a bug in WarpEM. However, according to
a colleague, the same procedure seem to work fine on windows.

I plan to attach a log file with default WINEDEBUG. Let me know if you need
further information.