New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing on Windows 10 due to lvcod64.dll #46
Comments
crash for my win7 64 bits too. |
Crash on Win 8.1 64 bit also as soon as I open the program |
Ditto. Instantly crashes on my Win10 x64 machine. *Edit: I should also mention I also tracked it down to something inside lvcod64.dll. |
Same |
OK. Apparently, lvcod64.dll is part of Logitech Webcam software. Uhm, I've got a Logitech webcam right under my monitor. Oh... Those of you who are experiencing crashes, who has Logitech webcams? Disconnecting mine, and then letting the software run, then reconnecting it, seems to have fixed it for now. Still, the fact that we need to dig for the crashing DLL... isn't particularly going to be helpful for the non-tech-savvy. |
I'm having the same problem. I can't even open the program. Any advice? |
Non tech-savy workaround for the time being:
On startup, it might show something like this (at least, it did for me, strangely. It didn't on my other computer where I didn't have Logitech issues though.): Now, the software is running on my laptop. Hopefully we can figure this out so it won't stumble on the dll in the future. ;) Hope this helps. |
I tryed renaming the .dll, I got to choose a different Video Device, the internal camera of my laptop(Lenovo Y5070) but immidiately crashed again afterwords. |
Is this problem still happening on the latest version? |
The program opens now yes! Thanks a ton! |
Wikid, will give it a go. |
removing the dll fixed it... but I kinda need my webcam. Did the merge above fix this? |
@falconmick Did you try the 1.0.1 build already? It fixed the logitech .dll for me and many others. |
Can confirm it fixed the Logitech issue for me as well. |
@3Rton I deleted boost and qt after I thought that the issue was my ability to read the JP install instructions wrong and just used the installer.. then I found out that I did compile it correct and it was this bug... Maybe later I will spend the year it took to download QT again! |
I used Window's built-in compatibility mode program by searching "Run programs made for previous versions of Windows" and that made it work for me. |
I've been getting the crash at start up with the install of Toonz 1.0.1 All the .dll fixes out there didn't work for me nor could I find any of the suggested .dll's to remove. Here's what I found has worked for me. So here's my workaround:
If you do forget and close on a Cintiq or secondary monitor simply delete the mainwindow.ini file Seems like a relatively simple fix. |
Well, the monitors issue is different than the DLL issue, and it sounds like the DLL issue has been resoved, but the monitor issue hasn't been fixed (as of yet). Could we close this issue, as all new posts seem to not be related to the DLL issue? |
I want to report that this old fix still resolves problems in 2022. Renaming the lvcod64.dll file fixes several crashes encountered to include startup and rendering to AV! format. |
Returning to this report. Here are some related reports in case they aren't linked above: |
This crash is has returned for many Opentoonz users in 2023. |
as allot of people are reporting https://groups.google.com/forum/#!topic/opentoonz_en/H8CDe_Uko6E I too cannot get this app to run either via my compilation or the installer. I keep getting this: link to exception message inside lvcod64.dll
When I attached my debugger I was able to see the line of code responsible but it really pissed me off (spent quite allot of time trying to get it running) so I deleted the source + qt + boost so I can't reproduce and connect debugger, unless you guys respond and ask me to re-do everything again (which I can)
I just don't know how responsive you will be so I don't want to spend another hr and have nobody reply to this bug.
EDIT:
I only have 1 screen plugged in
The text was updated successfully, but these errors were encountered: