On terça-feira, 2 de agosto de 2016 07:39:07 PDT Nilesh Kokane wrote:
> > What is you platform? How much memory you platform has?
>
> Windows 7. 8 GB Ram
If your application is 32-bit, it's limited to 2GB of virtual size anyway,
regardless of how much free memory you have.
--
Thiago Macieira
On Tue, Aug 2, 2016 at 12:49 AM, Igor Mironchik
wrote:
>
> Maybe you invoke AddToQueue very
> frequently, so your platform is not in time to process all images, so queue
> grows and at some time you are out of memory.
Yes, the call to the AddToQueue is very frequent
Hi,
What type of connection do you use for slot onImageReceived()?
If connection is queued then my guess can be correct.
On 01.08.2016 22:14, Igor Mironchik wrote:
Hi,
On 01.08.2016 20:19, Nilesh Kokane wrote:
On Aug 1, 2016 8:20 PM, "Igor Mironchik"
Hi,
On 01.08.2016 20:19, Nilesh Kokane wrote:
On Aug 1, 2016 8:20 PM, "Igor Mironchik" > wrote:
>
> Hi,
>
> You get this error in slot onImageReceived()?
No
> or you are talking about this lines:
>
>
> QImage img(cdata, 288, 352,
On Aug 1, 2016 8:20 PM, "Igor Mironchik" wrote:
>
> Hi,
>
> You get this error in slot onImageReceived()?
No
> or you are talking about this lines:
>
>
> QImage img(cdata, 288, 352, QImage::Format_RGB888);
> img = img.scaled(QSize(288*1.5,352*1.5));
> delete[]
In any way:
QImage::QImage(uchar <../qtcore/qtglobal.html#uchar-typedef>*data,
intwidth, intheight, Format format,
QImageCleanupFunction
cleanupFunction= Q_NULLPTR,
void*cleanupInfo= Q_NULLPTR)
Constructs an image with the
Hi,
You get this error in slot onImageReceived()?
or you are talking about this lines:
QImage img(cdata, 288, 352, QImage::Format_RGB888);
img = img.scaled(QSize(288*1.5,352*1.5));
delete[] cdata;
On 01.08.2016 17:24, Nilesh Kokane wrote:
Hello,
I've a function as follows. With
Hello,
I've a function as follows. With this I get QImage: out of memory,
returning null image, I dont allocate heap to QImage anywhere.
but the crash happens at QImage img(cdata, 288, 352,
QImage::Format_RGB888). Any clue.
If the QImage is allocating the memory to the heap internally how to free