We have had the same thing happening with failed Oracle connections. If I remember well, it happened when the correct Oracle client wasn't found or when the tns-name wasn't found. Could also be a timeout having caused the problem.
So yes, we've also seen disks completely filling up with dump files. What we do now, is delete them all when starting the application:
// v1, mjl, 18/03/19: delete "*_minidump_default_pid_*.*" files:
n_cst_dirattrib lnv_dirAttribs[]
n_cst_filesrv lnv_filesrv
long ll_fileCnt, ll_i
lnv_filesrv = create n_cst_filesrvunicode
ll_fileCnt = lnv_filesrv.of_dirlist( of_getappdir() + "\*_minidump_default_pid_*.dmp", 0 + 32, lnv_dirAttribs )
//messagebox('debug', of_getappdir() )
for ll_i = 1 to ll_fileCnt
setpointer(hourglass!)
try
fileDelete( of_getappdir() + "\" + lnv_dirAttribs[ll_i].is_filename )
catch ( runtimeerror rt)
// simply don't want to see any errors, hence the try catch
end try
next
//if ll_fileCnt > 0 then
// Messagebox("Information", string(ll_fileCnt) + " dump files have been deleted", information!)
//end if
setpointer(hourglass!)
destroy lnv_filesrv
regards,
MiguelL
thanks for the tip, unfortunately most of the time these dump files are created while the app is running (sometimes the app goes on, sometimes the app is freezing while the dump files are created).
Dum files of more than 500 MB are created each second, so the disk is full quite quickly.
its happens in executable and PB dev.