| 2015-06-29 07:01:48 |
James Henstridge |
bug |
|
|
added bug |
| 2015-06-29 07:02:01 |
James Henstridge |
attachment removed |
JournalErrors.txt https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1469611/+attachment/4421721/+files/JournalErrors.txt |
|
|
| 2015-06-29 09:01:58 |
James Henstridge |
bug |
|
|
added subscriber Albert Astals Cid |
| 2015-06-30 08:40:00 |
Albert Astals Cid |
bug |
|
|
added subscriber Timo Jyrinki |
| 2015-07-01 07:39:08 |
Albert Astals Cid |
qtdeclarative-opensource-src (Ubuntu): importance |
Undecided |
High |
|
| 2015-07-01 07:39:18 |
Albert Astals Cid |
qtdeclarative-opensource-src (Ubuntu): assignee |
|
Timo Jyrinki (timo-jyrinki) |
|
| 2015-07-01 07:39:22 |
Albert Astals Cid |
qtdeclarative-opensource-src (Ubuntu): status |
New |
Triaged |
|
| 2015-07-07 11:17:03 |
Timo Jyrinki |
qtdeclarative-opensource-src (Ubuntu): status |
Triaged |
In Progress |
|
| 2015-07-07 11:17:10 |
Timo Jyrinki |
bug task added |
|
qtdeclarative-opensource-src (Ubuntu RTM) |
|
| 2015-07-07 11:17:20 |
Timo Jyrinki |
qtdeclarative-opensource-src (Ubuntu RTM): assignee |
|
Timo Jyrinki (timo-jyrinki) |
|
| 2015-07-07 11:54:07 |
Timo Jyrinki |
qtdeclarative-opensource-src (Ubuntu RTM): importance |
Undecided |
High |
|
| 2015-07-07 11:54:10 |
Timo Jyrinki |
qtdeclarative-opensource-src (Ubuntu RTM): status |
New |
In Progress |
|
| 2015-07-08 05:46:13 |
Timo Jyrinki |
description |
While working on the new thumbnailer, we've been using the new QQuickAsyncImageProvider API. The API allows us to report errors by overriding the errorString() method on QQuickImageResponse to return a non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response->errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response->errorString();
} else {
t = response->textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job->postReply(error, errorString, t->textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then dereferenced to call t->textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago) |
While working on the new thumbnailer, we've been using the new QQuickAsyncImageProvider API. The API allows us to report errors by overriding the errorString() method on QQuickImageResponse to return a non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response->errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response->errorString();
} else {
t = response->textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job->postReply(error, errorString, t->textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then dereferenced to call t->textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago)
Test case:
- bzr branch lp:~jamesh/thumbnailer/no-fallback-albumart
- build the branch
- run ctest -R qml --verbose
-> crash or no crash (don't mind pass/fail) |
|
| 2015-07-08 07:13:31 |
Timo Jyrinki |
description |
While working on the new thumbnailer, we've been using the new QQuickAsyncImageProvider API. The API allows us to report errors by overriding the errorString() method on QQuickImageResponse to return a non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response->errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response->errorString();
} else {
t = response->textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job->postReply(error, errorString, t->textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then dereferenced to call t->textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago)
Test case:
- bzr branch lp:~jamesh/thumbnailer/no-fallback-albumart
- build the branch
- run ctest -R qml --verbose
-> crash or no crash (don't mind pass/fail) |
While working on the new thumbnailer, we've been using the new QQuickAsyncImageProvider API. The API allows us to report errors by overriding the errorString() method on QQuickImageResponse to return a non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response->errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response->errorString();
} else {
t = response->textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job->postReply(error, errorString, t->textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then dereferenced to call t->textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago)
Test case (on desktop):
- bzr branch lp:~jamesh/thumbnailer/no-fallback-albumart
- sudo apt-get build-dep thumbnailer
- sudo apt install libleveldb-dev cmake-extras libapparmor-dev libboost-filesystem-dev libboost-regex-dev libqtdbustest1-dev libunity-api-dev python3-tornado qml-module-qttest xvfb
- cd no-fallback-albumart
- cmake .
- make
- ctest -R qml --verbose
-> check if crash (Aborted core dumped) or no crash (don't mind pass/fail) |
|
| 2015-07-08 08:08:14 |
Timo Jyrinki |
description |
While working on the new thumbnailer, we've been using the new QQuickAsyncImageProvider API. The API allows us to report errors by overriding the errorString() method on QQuickImageResponse to return a non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response->errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response->errorString();
} else {
t = response->textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job->postReply(error, errorString, t->textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then dereferenced to call t->textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago)
Test case (on desktop):
- bzr branch lp:~jamesh/thumbnailer/no-fallback-albumart
- sudo apt-get build-dep thumbnailer
- sudo apt install libleveldb-dev cmake-extras libapparmor-dev libboost-filesystem-dev libboost-regex-dev libqtdbustest1-dev libunity-api-dev python3-tornado qml-module-qttest xvfb
- cd no-fallback-albumart
- cmake .
- make
- ctest -R qml --verbose
-> check if crash (Aborted core dumped) or no crash (don't mind pass/fail) |
While working on the new thumbnailer, we've been using the new QQuickAsyncImageProvider API. The API allows us to report errors by overriding the errorString() method on QQuickImageResponse to return a non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response->errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response->errorString();
} else {
t = response->textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job->postReply(error, errorString, t->textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then dereferenced to call t->textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago)
Test case (on desktop):
- bzr branch lp:~jamesh/thumbnailer/no-fallback-albumart
- sudo apt-get build-dep thumbnailer
- sudo apt install libleveldb-dev cmake-extras libapparmor-dev libboost-filesystem-dev libboost-regex-dev libqtdbustest1-dev libunity-api-dev python3-tornado qml-module-qttest xvfb
- cd no-fallback-albumart
- cmake .
- make
- ctest -R qml --verbose
-> check if crash (Segmentation fault (core dumped)) or no crash (don't mind tests pass/fail) |
|
| 2015-07-08 09:20:49 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/wily-proposed/qtdeclarative-opensource-src |
|
| 2015-07-13 12:48:30 |
Launchpad Janitor |
qtdeclarative-opensource-src (Ubuntu): status |
In Progress |
Fix Released |
|
| 2015-07-15 08:16:14 |
Timo Jyrinki |
qtdeclarative-opensource-src (Ubuntu RTM): status |
In Progress |
Fix Released |
|
