-
Notifications
You must be signed in to change notification settings - Fork 11
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
Wonderwall segfault #37
Comments
I get the same segfault when attempting to view an email in Trojitá using this QtWebkit implementation.
The crash occurs because
webkit/Source/WebCore/platform/graphics/PlatformPath.h Lines 41 to 42 in 2d2b379
webkit/Source/WebCore/platform/graphics/Path.cpp Lines 412 to 415 in 2d2b379
webkit/Source/WebCore/platform/graphics/qt/PathQt.cpp Lines 113 to 116 in 2d2b379
The offending commit was 71a469f. |
`WebCore::Path::platformPath()` expects to be able to return the return value of `WebCore::PlatformPathImpl::platformPath()` as a `PlatformPathPtr` without creating a dangling reference. However, `WebCore::PathQt::platformPath()` is defined as returning a temporary `QPainterPath` object, which does become a dangling reference when returned by reference, leading to segfaults at runtime. This commit changes the return type of `WebCore::PathQt::platformPath()` to `PlatformPathPtr` (paralleling the definition of `WebCore::PathCG::platformPath()`), so as to avoid creating a temporary `QPainterPath` object, thereby avoiding the creation of a dangling reference when returning from `WebCore::Path::platformPath()`. Fixes: movableink#37
Hi,
I was attempting to start Wonderwall (from the aur) with the qt5-webkit-movableink-git instead of the normal qt5-webkit. I did this by installing the prebuilt package uploaded onto Sourceforge several days ago, and then altering the wonderwall pkgbuild to reflect this dependency instead of qt5-webkit. It did not start, and I got a segfault. The information, including a backtrace, is printed below:
backtrace.txt
The program works with qt5-webkit.
The text was updated successfully, but these errors were encountered: