Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.2f1
Issue ID
893325
Regression
No
Failed to load .DLL file, because the specified procedure could not be found
Repro steps:
1. Open provided projects "cef_test" scene
2. Enter Play mode
3. Press on the "Button" in the Game view
4. Look at the Console
Expected result: For the .dll file to be found and for errors to not appear
Actual result: .dll file not found resulting in a lot of errors
Reproduced with: 2017.1.0b3, 2017.1.0b2, 2017.1.0b1, 2017.1.0a6, 5.6.0p3, 5.6.0p2, 5.6.0p1, 5.6.0f3, 5.5.3p2, 5.5.3p1, 5.5.3f1, 5.5.2f1, 5.5.1f1, 5.4.5p1, 5.4.5f1, 5.4.0f3, 5.3.8f1
Note:
Added a video of repro and errors
The .DLL file can be found inside of Unity install, in Editor folder. (It's called libcef.dll)
Comments (1)
-
koeiandy
Mar 21, 2018 09:15
1. launch Editor
2. put some dll into Assets/Plugins
3. press play.
then console show the error as same as this report.but if I close editor and restart it, the dll will work well without any error.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The search field has an additional icon that has no functionality
- Splash Image logo is shown after being removed when pressing the Preview button
- Crash on GenerateParticleGeometry when creating certain particles
- HD Sample Buffer returns black for Rendering Layer Mask when Custom Pass Volume is not active
- SpriteRenderer has wrong input color when associated material uses SRPBatcher
Resolution Note:
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being as this is quite low priority since it's touching CEF modules. We understand that this will cause problems for some users, and so may address in a future version.