![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Problem with Adobe Shockware Flash Plugin "Message from dll" "Can't create FileMapping"
Hi,
I have a problem with Adobe Shockware Flash 11.9.900.152 Plugin on Mozilla Firefox 25.0.1 on Windows 7 Ultimate (x64).
Every first time I start Firefox and enter a site that required flash player, I get this message.
http://i.imgur.com/rQyXONx.png
"Message from dll" "Can't create FileMapping"
The message only display in the first time I run Firefox after startup then enter a site that require flash player. It won't display again until I restart my computer or log out then log in my Windows account again.
I tried to disable/uninstall Adobe Shockware Flash Plugin and restart then run Firefox again, the message doesn't display anymore.
But when I enable/reinstall Adobe Shockware Flash Plugin and restart then run Firefox again, the message display again.
I tried to uninstall Firefox + Adobe Shockware Flash Plugin and reinstall them. But the problem still happen.
Only Firefox got the problem, Internet Explorer and Google Chrome doesn't.
Thanks in advance!!
Alle Antworten (4)
hello hinotama, based on your screenshot it rather looks like this error message is coming from the flash plugin process itself & not from firefox.
to troubleshoot such an issue, it would be best to contact adobe's support & file a bug report at bugbase.adobe.com (choose "Adobe Flash Player" as the product & "Browser Integration" as the product area), since they will have a better understanding of the internals of the plugin & therefore may know what might be at the root of the problem you were seeing and are the only ones able to fix it.
Did you uninstall the Flash player as well?
Note that this will remove all installed Flash players.
Thanks for your replies!
@philipp: As you have suggested, I've submitted a bug and now I'm waiting for it to be verified.
@cor-el: Yes, I tried that too. But the problem still occurred after I reinstall it again.
thank you for reporting back - for cross-reference, here's the filed bug at adobe: https://bugbase.adobe.com/index.cfm?event=bug&id=3681184