On Sep 26, 2014, at 8:43 AM, Helmut Mülner wrote:
> […]
> ... because copy() failed (because malloc failed) and d was 0 and led to a
> null pointer access.
> This is a bug in QImage that should be fixed.
Is Qt ever expected to “act sanely” in face of memory allocation failures? Is
there a polic
I am developing a mixed C++/QML application using
qt-opensource-windows-x86-msvc2012_opengl-5.3.2 (and 5.4.0-beta).
The QML GUI contains a zoomable Canvas item embedded in a ScrollView.
Zooming the Canvas changes its size, and after experiencing some strange
crashes of the application during zoomi
