<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NL" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">> Looking at your core file, it appears as though this may be from an application whose virtual address space is larger than 8GB.
</span>See a recently known issue about this:<o:p></o:p></p>
<p class="MsoPlainText">> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_diamon_minicoredumper_issues_6&d=DwICAQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=5N90rj6avleIhhFOAVczeXUO76NE29a_GTjIG_9KNVQ&m=QRpDcUlCKsD41Fj2PKPp6a-1p-OfKYk7zW2Y800WrNg&s=e0mnCL2-L5QICuITU-OgLp_FUdFjBkV0FVMXjkGfmVU&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_diamon_minicoredumper_issues_6&d=DwICAQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=5N90rj6avleIhhFOAVczeXUO76NE29a_GTjIG_9KNVQ&m=QRpDcUlCKsD41Fj2PKPp6a-1p-OfKYk7zW2Y800WrNg&s=e0mnCL2-L5QICuITU-OgLp_FUdFjBkV0FVMXjkGfmVU&e=</a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:black">John,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black">Thanks for your investigation. Happy that we now at least have a clear where the issue comes from. Our application processes up to a few thousand live camera images per second and can easily claim
over 60 GB of memory... Let's just say we have good reasons why we would like to use minicoredumper
</span><span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif;color:black">😊</span><span lang="EN-US" style="color:black">
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black">Unfortunately, your proposed solution to dump directly into gzip is not an option for us, since we have to send the core dumps from sites like rural Africa/Australia over connections with less than
desired upstream bandwidth. We know that gzip will have a tough time compressing our memory data, and the slow compression process will cause longer downtime of the system.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black">Jos<o:p></o:p></span></p>
</div>
</body>
</html>