reassign 666742 libxine2
thanks
Thanks for jumping in, Darren, and thanks to Tobias for finding the root
cause.
Small email to reassign the bug to the right package, and, of course, I'd
be more than happy to test soon your new version in experimental ;-)
This said, I understand the point of being
You wrote:
> On 27/04/13 18:40, Tobias Grimm wrote:
>> # xvinfo | grep -i "image size"
>> maximum XvImage size: 4096 x 4096
> Yep, my integrated Intel Graphic (on both my PCs), shows:
> maximum XvImage size: 2048 x 2048
>> I don't have a solution for this at hand, but will forward this issue
Hi,
On 27/04/13 18:40, Tobias Grimm wrote:
# xvinfo | grep -i "image size"
maximum XvImage size: 4096 x 4096
Yep, my integrated Intel Graphic (on both my PCs), shows:
maximum XvImage size: 2048 x 2048
I don't have a solution for this at hand, but will forward this issue
upstream. Obvious
Hello!
I think I know what's going wrong.
libxine uses XvShmCreateImage to create images, but somehow the image size
is limited. XvShmCreateImage then creates a smaller image and libxine runs
into a segfault, when trying to fill the image data with larger image data.
The max image size seems to
4 matches
Mail list logo
