Years back, I had a strange graphics problem in MOUL that seemed to have been caused by an OSX automatic update not playing well with an unknown app setting(s). Although the cause and cure were never determined, the workaround which fixed the problem was to create a fresh OSX profile and port my apps from the old to the new. It might be worthwhile to experiment with this and see if it helps.
Since it is an experiment at this point, I'd suggest that you only port the DI wrapper to a different profile and test the wrapper from there.
Also, some other obvious suggestions (just to cover all the bases), ensure that no unnecessary apps are running simultaneously. Especially if you have a limited amount of memory installed, the newer OSX versions make varying levels of demand on system memory. Mavericks was especially bad at handling memory well (though others will disagree with this opinion) and would frequently top out my system and slow things to a grinding halt when I was exploring online. Yosemite (my current OS) is much better at handling memory. Even so, I find it makes a big difference to ensure that non-essential apps are shut down when I am online.
In my current OS (Yosemite), kernel_task, Finder and browsers can be big memory hogs. For the best online performance, I like to close down all my non-essential apps, reboot and then log in from there. A fresh boot will ensure that kernel_task and Finder are using minimal memory.
Hope some of this helps. Keep us posted about your progress!