I normally use WryeBash standalone, but decided to install the full considering I had Python already on my system for PyFFi.

Usually I would launch my game directly from the OBSE Loader, but the little feature on WryeBash to just click the icon made it easy for me to do this especially while messing around with my mod lineup. This morning while doing this, my game was crashing a lot after an hour or so of play. I decided to check task manager and noticed that Python was using over 700mb of RAM, and climbing rapidly even without doing anything.

Whether this was just an isolated incident, or WryeBash/Python having memory leak issues, I'm not sure. Needless to say it doesn't require rocket science to explain that losing nearly 25% of my RAM just to power the program in the background because I launched OBSE through it was robbing Oblivion of precious resources necessary to run smoothly. If I launch OBSE directly, Python isn't required, and thus no chance for it to do this.

Summary: If you run WryeBash in the background while playing and frequently experience crashing, try closing it unless you're actually using the tool.

You can enable 'auto-quit' in Bash (click on the pink square on the left in the status bar of Bash), which closes down Bash when you start Oblivion through it. Best of both worlds: convenience of starting Oblivion through Bash without the performance hit of running Bash in the background.