BAM does not do anything inside Dreamweaver. If you are referring to Live View, then that is just Dreamweaver pretending it is a browser. I'm not sure you are understanding how Dreamweaver works and how extensions work... but if it helps, you should avoid Live View. It is not a very stable environment. It might also help you in getting responses from others if you disclose your version of Dreamweaver, your OS, and as many details as you can with regard to your workflow.

Thanks Al,
My version of Dreamweaver is CC newest build; OS is Win 10 with all the latest updates; an i5-4570 processor with 12 gig of memory. Funny how it is only BAM that causes this in "live" view, Background image rotator does not, nor any of the other P7 products I use.

I'm not sure what you are inferring, but we've been doing this for 20 years and are pretty thorough in testing. We cannot duplicate an issue. While my two Windows 10 machines use i7 processors with fairly high end video cards, I cannot duplicate an issue. That said, none of here would ever consider using Dreamweaver 18 for real work. We install it for testing only and use the last stable version of Dreamweaver for actual production work. I do notice that everything slows down in CS6 Live View, but BAM is neither better nor worse than any other active script. Dreamweaver is simple not a real browser and live view is as poorly programmed as the CSS rendering support in straight Design View.

I would not consider this an issue that has a solution. The thing is, that without being able to reproduce things, we have to chalk it up to either a local system issue or another in a long line of Adobe programming flaws.