That was from royale-asjs jenkins project There are also several in royale-asjs_jsonly royale-asjs/frameworks/js/projects/MXRoyaleJS/hs_err_pid5136.mdmp 683M royale-asjs/frameworks/js/projects/TLFJS/hs_err_pid4508.mdmp 570M royale-asjs/frameworks/js/projects/MXRoyaleJS/hs_err_pid5136.log royale-asjs/frameworks/js/projects/MXRoyaleJS/replay_pid5136.log royale-asjs/frameworks/js/projects/TLFJS/hs_err_pid4508.log royale-asjs/frameworks/js/projects/TLFJS/replay_pid4508.log royale-typedefs/js/hs_err_pid5196.log royale-typedefs/js/replay_pid5196.log
On Tue, Jan 22, 2019 at 4:00 PM mrchnk <mrc...@gmail.com> wrote: > Hello, > > There were some issues with compilation on official jenkins ci ( > http://apacheroyaleci.westus2.cloudapp.azure.com:8080/) > So some huge minidump reports were created: > > royale-asjs/frameworks/js/projects/MXRoyaleJS/hs_err_pid21764.mdmp 283 MB > royale-asjs/frameworks/projects/MXRoyale/hs_err_pid20992.mdmp 694 MB > > Along with some log files: > > royale-asjs/frameworks/js/projects/MXRoyaleJS/hs_err_pid21764.log > royale-asjs/frameworks/js/projects/MXRoyaleJS/replay_pid21764.log > royale-asjs/frameworks/projects/MXRoyale/hs_err_pid20992.log > royale-asjs/frameworks/projects/MXRoyale/hs_err_pid456.log > royale-asjs/frameworks/projects/MXRoyale/replay_pid20992.log > royale-asjs/frameworks/projects/MXRoyale/replay_pid456.log > royale-typedefs/js/hs_err_pid5196.log > royale-typedefs/js/replay_pid5196.log > > These dumps and logs continue to be included in artifacts and artifacts > grow drastically. > Also, it is not related to any latest build. >
