How to avoid generating java.log files and matlab_crash_dump.xxxx files?

Greetings,

I am running my programs based on parallel computation on clusters.

After program finished, I always got lots of java.log.xxxx files or sometimes matlab_crash_dump.xxxx files. Usually, I need to mannually delete them. Sometimes, when I deleted them, my programs and data were also deleted automatically, which was not I expected.

Is there any way to avoid generate these files?

%Example of java.log.xxxx files   
Operating System: Linux 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64
  Processor ID:     x86 Family 6 Model 79 Stepping 1, GenuineIntel
  Host Name:        gra121
Picked up _JAVA_OPTIONS: -Xmx256m




%Example of matlab_crash_dump.xxxx files   

--------------------------------------------------------------------------------
       Segmentation violation detected at Thu Oct 10 11:11:23 2019 -0400
--------------------------------------------------------------------------------

Configuration:
  Crash Decoding           : Disabled - No sandbox or build area path
  Crash Mode               : continue (default)
  Default Encoding         : UTF-8
  Deployed                 : false
  GNU C Library            : 2.24 stable
  Graphics Driver          : Unknown software 
  Java Version             : Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
  MATLAB Architecture      : glnxa64
  MATLAB Entitlement ID    : 707954
  MATLAB Root              : /cvmfs/restricted.computecanada.ca/easybuild/software/2017/Core/matlab/2018a
  MATLAB Version           : 9.4.0.813654 (R2018a)
  OpenGL                   : software
  Operating System         : "CentOS Linux release 7.5.1804 (Core) "
  Process ID               : 11006
  Processor ID             : x86 Family 6 Model 79 Stepping 1, GenuineIntel
  Session Key              : 02a3602b-8707-4c8a-9fe9-36f42410a899
  Static TLS mitigation    : Disabled: Unable to open display
  Window System            : No active display

Fault Count: 1


Abnormal termination

Register State (from fault):
  RAX = 0000000000000000  RBX = 00002b4253fff4b0
  RCX = 00002b42540005c0  RDX = 0000000000000048
  RSP = 00002b4253fff450  RBP = 00002b4253fff490
  RSI = 00002b424c0102d0  RDI = 0000000000000000

   R8 = 00002b4220bc23d8   R9 = 0000000000000000
  R10 = 00002b424c0102d0  R11 = 00002b43f01a9c80
  R12 = 00002b4253fff460  R13 = 00002b435679f650
  R14 = 00002b42541c76f0  R15 = 00002b4253fff5d0

  RIP = 00002b430cc16dd1  EFL = 0000000000010246

   CS = 0033   FS = 0000   GS = 0000

Stack Trace (from fault):
[  0] 0x00002b430cc16dd1                        bin/glnxa64/libmwhgutils.so+00626129 _ZN7hgutils17BaseObjectCOSInfo9getClientEv+00000001
[  1] 0x00002b430c249225                             bin/glnxa64/libmwhg.so+02396709
[  2] 0x00002b430c266788                             bin/glnxa64/libmwhg.so+02516872
[  3] 0x00002b430c2669b7                             bin/glnxa64/libmwhg.so+02517431
[  4] 0x00002b430c2b7945                             bin/glnxa64/libmwhg.so+02849093
[  5] 0x00002b430c3cb3b8                             bin/glnxa64/libmwhg.so+03978168
[  6] 0x00002b430c42db09                             bin/glnxa64/libmwhg.so+04381449
[  7] 0x00002b4222544586                       bin/glnxa64/libmwservices.so+03265926
[  8] 0x00002b4222544ff2                       bin/glnxa64/libmwservices.so+03268594
[  9] 0x00002b42225458fb                       bin/glnxa64/libmwservices.so+03270907 _Z25svWS_ProcessPendingEventsiib+00000187
[ 10] 0x00002b423aaa7fc3                            bin/glnxa64/libmwmcr.so+00647107
[ 11] 0x00002b423aaa86a4                            bin/glnxa64/libmwmcr.so+00648868
[ 12] 0x00002b423aaa13f1                            bin/glnxa64/libmwmcr.so+00619505
[ 13] 0x00002b4224cee1f4 /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libpthread.so.0+00029172
[ 14] 0x00002b42233fb16f /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6+00950639 clone+00000095
[ 15] 0x0000000000000000                                   <unknown-module>+00000000