Issue with avutil-50.dll and chrome

Thu, 02/25/2010 - 12:10 — pstretz

Issue tracking here, http://code.google.com/p/chromium/issues/detail?id=35857 didn't know if there was anything the electric sheep team could do.

Wed, 04/28/2010 - 12:24 — happyenduser

same issue with google chrome

just posting my data relating to the error message, this happened when i upgraded to the latest beta version [5.0.342.9] of Chrome today. the error message that pops up during Chrome launch is:


[title bar] chrome.exe - Entry Point Not Found

[message text] The procedure entry point av_get_pix_fmt could not be located in the dynamic link library avutil-50.dll

i am using Windows 7 Ultimate 64x, latest service packs installed as of 4/28/2010.

i tried copying the avutil-50.dll from the chrome directory into windows/system32; this did not resolve issue.

i also installed latest version of electric sheep, listed above; this also did not resolve issue.

uninstalling electric sheep to see if problem is resolved.

Wed, 04/28/2010 - 12:34 — happyenduser

While going to uninstall Electric Sheep, I noticed I had two versions installed.
I uninstalled the original one, and left the updated [latest] version mentioned in this thread installed.
Google Chrome immediately started working without even having to close the browser. No reboot was needed. :D

Sat, 03/27/2010 - 06:58 — GeoJunkie

Me Too - tricky fix

Ran into this issue this morning on Vista 32 with Chrome 5.0.342.8 beta. Took several tries to get it to fix. Simply upgrading Electric Sheep or uninstalling then installing the upgrade didn't help. I had to uninstall, reboot, delete the avutil-50.dll from the Windows directory, then install the upgraded Electric Sheep. Problem solved!

Fri, 02/26/2010 - 16:58 — spot

thanks for the bug report.

thanks for the bug report. the next release statically links that library, which solves the problem. it will be out in a few days.

Fri, 02/26/2010 - 16:44 — cd

New version will not use this

New version will not use this dll anymore. There are other features that are still not fully tested, but it will be ready soon.

Problem is caused by chrome using "our" dll and at the same time by us, putting this dll in windows folder.

This dll is part of ffmpeg, so it could be in conflict with other software (video players, encoders) or plugins for browsers with similar functionality. Copying it will not help, because we need specific version and other programs need different one.

Fri, 02/26/2010 - 15:30 — ryannosaurus.rexx

I posted over on the Google

---EDIT---
Dangit, spoke too soon. It just started popping up again. Sorry!!
---EDIT---

I posted over on the Google code page, but wanted to mention here as well... I had the problem until I updated to the latest Electric Sheep. Problem solved! Chrome and Electric Sheep now work fine. (At least on my Win7 x64 Pro...)

Get it here:

http://community.electricsheep.org/download

HIH.

Thu, 02/25/2010 - 23:22 — agapecs

Same here

I was the poster of the bug; seems like a uninstall of eletricsheep fixes the issue with Chrome. I think I speak for everyone in saying we don't want to give up our sheep. Any possible workaround or fix? Will update likewise if the Chrome team finds a fix.

Thu, 02/25/2010 - 20:07 — bksening

As the bug report says, the

As the bug report says, the problem in caused by the avutil-50.dll that Electric Sheep places in the Windows directory.

Thu, 02/25/2010 - 16:04 — skamradt

also experiencing the same

also experiencing the same problem, unfortunately had to disable running sheep for now until its fixed.

Tue, 06/01/2010 - 18:28 — Eric W.

XP x64

Experiencing the same on XP x64. Happened mysteriously over the weekend. Wasn't fixed by installing the latest version of electric sheep at:

http://community.electricsheep.org/download.

I have to uninstall electric sheep, but I really don't want to. It's one of my favorite non-essential programs.

Tue, 06/01/2010 - 18:30 — Eric W.

Fixed!

I see now that I had two versions of electric sheep installed in parallel. When I removed the older version, the problem seems to have gone away. :)

Thu, 03/11/2010 - 18:08 — skamradt

Problem resolved

The latest version corrects the problem. Oh, and I now have three screens running without any issues, the 3rd screen was added by using this little usb device http://www.evga.com/products/moreInfo.asp?pn=100-U2-UV16-A1&family=USB . Works like a charm...I strongly recommend for anyone considering adding another monitor. Using digital cables and other than a tiny jump here and there, it keeps up!

Fri, 03/12/2010 - 18:06 — spot