Skip to content
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

ffmpeg + gcc 4.8.x dec_avcodec compatibility on win32 #628

Closed
totaam opened this issue Aug 7, 2014 · 12 comments
Closed

ffmpeg + gcc 4.8.x dec_avcodec compatibility on win32 #628

totaam opened this issue Aug 7, 2014 · 12 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Aug 7, 2014

Issue migrated from trac ticket # 628

component: platforms | priority: major | resolution: wontfix | keywords: win32

2014-08-07 10:34:59: totaam created the issue


Despite compiling without warnings against both ffmpeg 2.3 and 2.3.1, the resulting dec_avcodec2 video decoder module causes cleanup errors on exit on win32. (that look like use after free or memory corruption: memory accesses at low addresses like 0x00000004)

I think it is safer to go with the 2.2.x branch (2.2.6 is out), even on OSX and Linux: done in r7175.
Please confirm that the problem exists with 2.3 on win32 and re-assign to me as non-blocker for 0.15.

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 10:27:40: totaam commented


Note: may not be a bug, was seeing the same thing with 2.2.6, a good old reboot-windows later and it's gone..

Found some xpra cleanup bugs, fixed in r7199 (will backport).

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 11:45:32: totaam commented


Well, well, well.

There is a problem, but it is not with the ffmpeg version.
I made a fresh 2.2.5 build (using the exact same command line) and it exhibits the same problem at runtime, the "old" 2.2.5 one does not.

Diffing the two trees shows absolutely nothing of interest, the only files shown as being different are the ".lib", ".a" and ".dll" - which is kind of expected.

So it must be a toolchain related bug. GCC got updated to 4.8.x in mingw32 recently (mingw-get update;mingw-get upgrade...).
It could be a bug in GCC or maybe the newer GCC turns on some stricter checks in the ffmpeg code.
Disabling w32threads makes no difference.

So, now we downgrade GCC back to 4.7, except the downgrade breaks mingw...
You have to download the few dlls that go MIA yourself from here: [http://sourceforge.net/projects/mingw/files/MinGW/Base/].
And miracle, it no longer crashes.

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 12:18:30: totaam changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 12:18:30: totaam changed title from ffmpeg 2.3.x dec_avcodec compatibility to ffmpeg + gcc 4.8.x dec_avcodec compatibility on win32

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 12:18:30: totaam changed priority from blocker to major

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 12:18:30: totaam changed owner from smo to totaam

@totaam
Copy link
Collaborator Author

totaam commented Aug 8, 2014

2014-08-08 12:18:30: totaam commented


(updating bug title)

@totaam
Copy link
Collaborator Author

totaam commented Apr 14, 2015

2015-04-14 17:06:34: antoine commented


I don't have time for toolchain issues.

@totaam
Copy link
Collaborator Author

totaam commented Jan 23, 2016

2016-01-23 05:51:51: antoine commented


FWIW: tried again today and it still causes crashes. Either building ffmpeg with gcc 4.8, or building the cython modules that link to it triggers crashes.

@totaam
Copy link
Collaborator Author

totaam commented Sep 27, 2016

2016-09-27 10:07:21: antoine changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Sep 27, 2016

2016-09-27 10:07:21: antoine set resolution to wontfix

@totaam
Copy link
Collaborator Author

totaam commented Sep 27, 2016

2016-09-27 10:07:21: antoine commented


Superseded by #678.

Closing as wontfix: this build system will remain as it is for now, not updating gcc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant