This morning I updated Vista Sp2 Home Premium and Xp Sp3 machines to new flash version. IE8 both machines.

After update, Defensewall works as previous on XP machine but Defensewall on Vista shows a major pattern change.

Before update, Defensewall would show one untrusted FlashUtil10c.exe for each running process on an opened web page. When the web page would close, Defensewall would release each flash.exe process and the number of untrusted processes would decline. With new flash version 32.18, each flash.exe shows as untrusted in Defensewall but the flash.exe does not release when closing a page. Opening new web pages with flash, adds more and more untrusted processes in Defensewall, only closing IE exits the untrusted processes.

I suspect this is an adobe change, because a review of task manager in vista shows many more open FlashUtil10c.exe processes than previous flash versions.

Updated flash on Firefox shows no pattern change to previous versions.

Edit: Further study shows that turning OFF Defensewall releases the FlashUtil10c.exe processes in task manager when web pages close, so it appears there may be a conflict with Defensewall, at least on my machine.

Hello,

My experience:

• If, with IE8, I open two tabs with this page: http://secunia.com/vulnerability_scanning/online/ , I have two Untrusted java.exe .
• If I close 1 tab, I have only one Untrusted java.exe.

OS: Windows XP SP3
Flash: 10.0.32.18
DW: 2.56

How to reproduce the issue?

OK, the issue is absolutely clear. As you said, it's Adobe's programmers who didn't do their home exercises. Normally, they had to close all the COM references to the object, but they didn't do this. That's why you can see those "left" processes as DW do separates COM-running instances of the processes.

Any solution?

http://forums.adobe.com/thread/471057?tstart=0

Thanks, I noticed they didn't reply in a "flash".