Terminal doesn't use custom bash profile when debugging

redirected here from closed issue https://github.com/microsoft/vscode/issues/80434
The bug appeared after one of few last updates.
When integrated terminal starts it uses custom profile (as expected),
but after python script is started it loads profile from ~/.bashrc

In my settings.json I have the following settings:

"terminal.integrated.shellArgs.osx": [
   "--rcfile", "/Volumes/DISK/projs/TechStuff/settings/profile"
],
"terminal.integrated.env.osx": {"HISTFILE":"/dev/null"},
"terminal.integrated.setLocaleVariables": false,

Environment data

Version: 1.38.0
Commit: 3db7e09f3b61f915d03bbfa58e258d6eee843f35
Date: 2019-09-03T21:47:00.464Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.7.0

Expected behaviour

using custom profile (environment)

Actual behaviour

using standard profile (environment), after starting python script

Steps to reproduce:

1. Assign custom profile to integrated terminal settings.(and restart maybe)
2. Open page(tab) with any python script and open integrated terminal.
   (You can put string like echo 'bashrc loaded' in profile file to see it loads)
3. Check profile - it is cutom.
4. Debug python script (F5 or Debug -> Start Debugging) - it loads bashrc profile instead of custom
5. Check which profile is loaded (can use printenv command if you set different env. variables or check echo print as mentioned above) - standard profile loaded.

Beginne damit, das Problem mit den aufgeführten Einstellungen für terminal.integrated.shellArgs.osx, einer benutzerdefinierten --rcfile und einem Python-Debug-Start mit F5 zu reproduzieren. Vergleiche die Umgebung des integrierten Terminals mit der Umgebung, nachdem das Debugging gestartet wurde. Als abgeschlossen gilt die Aufgabe, wenn der durch das Debugging gestartete Prozess das konfigurierte benutzerdefinierte Profil beibehält, statt ~/.bashrc zu laden.