Save QImage from BYTE buffer segfaults ?

R-P-H

@Kent-Dorfman said in Save QImage from BYTE buffer segfaults ?:

FWIW, you cannot make the absolute assumption that buf will be 32bit word aligned. If I had to guess, that would be my guess as to why it crashes sometimes. The Qt docs ae specific about the need for buf to be 32bit word aligned.

Yes I saw that in the documentation. I assumed that if buffer is being populated the same way each time and that if it works sometimes, then it should be fine.

Does Qt have any other way to get around this besides using another image processing library to save the image ?

SGaist

What are you using to fill that buffer ?
Where do these data come from ?

R-P-H

@SGaist said in Save QImage from BYTE buffer segfaults ?:

What are you using to fill that buffer ?
Where do these data come from ?

It's populated using an API call which finishes successfully. So I can only interrogate the validity of the data after its completed.

SGaist

That's a bit short on details. An API call can be a method from a library your are using or a remote call to a REST service.

What kind of image are you getting ?

Christian Ehrlicher

@R-P-H said in Save QImage from BYTE buffer segfaults ?:

I assumed that if buffer is being populated the same way each time and that if it works sometimes, then it should be fine.

Even if it does it would depend on your image size (or better: bytes per line). If it's a multiple of 4 it does not crash, if it's something else the alignment is wrong.

R-P-H

@SGaist said in Save QImage from BYTE buffer segfaults ?:

That's a bit short on details. An API call can be a method from a library your are using or a remote call to a REST service.

What kind of image are you getting ?

It's from a library. The API reference is very short on details. It's a 256 gray-level image.

R-P-H

@Christian-Ehrlicher said in Save QImage from BYTE buffer segfaults ?:

@R-P-H said in Save QImage from BYTE buffer segfaults ?:

I assumed that if buffer is being populated the same way each time and that if it works sometimes, then it should be fine.

Even if it does it would depend on your image size (or better: bytes per line). If it's a multiple of 4 it does not crash, if it's something else the alignment is wrong.

The image size is always the same (260 x 300 px).

SGaist

And one byte per pixel ?

R-P-H

@SGaist said in Save QImage from BYTE buffer segfaults ?:

And one byte per pixel ?

That is correct yes.

SGaist

Can you get the stack trace of the crash ?

R-P-H

@SGaist said in Save QImage from BYTE buffer segfaults ?:

Can you get the stack trace of the crash ?

I'm testing the application on another machine using the executable. I don't think I'd be able to get it without QT or another IDE right ?

SGaist

Windows machine ?

R-P-H

@SGaist said in Save QImage from BYTE buffer segfaults ?:

Windows machine ?

Yes it is. Windows 7 and also Windows 10.

mranger90

try:
BYTE *buf = new BYTE[imWidth * imHeight];

R-P-H

@mranger90 said in Save QImage from BYTE buffer segfaults ?:

try:
BYTE *buf = new BYTE[imWidth * imHeight];

Hi, it is not crashing anymore, however the image seems to be coming out completely black. I will confirm tomorrow if the image is supposed to be completely black or not...

Jarek B

From the documentation
https://doc.qt.io/qt-5/qimage.html#QImage-4
data must be 32-bit aligned, and each scanline of data in the image must also be 32-bit aligned.

So (as far as I understand) that is not enough to have memory buffer aligned to 32 bit address, also each line have to be aligned to 32 bit address. So if you have image that is 260x300 pixels, a whole line will take 288 bytes. So for whole image you should have 288*300 bytes which is more than you have provided.

R-P-H

@Jarek-B said in Save QImage from BYTE buffer segfaults ?:

From the documentation
https://doc.qt.io/qt-5/qimage.html#QImage-4
data must be 32-bit aligned, and each scanline of data in the image must also be 32-bit aligned.

So (as far as I understand) that is not enough to have memory buffer aligned to 32 bit address, also each line have to be aligned to 32 bit address. So if you have image that is 260x300 pixels, a whole line will take 288 bytes. So for whole image you should have 288*300 bytes which is more than you have provided.

Hi, interesting...I have not seen any examples like that. How are you arriving at 288 bytes ? Are you suggesting I make the buffer 288x300 bytes instead ?

mranger90

@R-P-H Of course it's black, the data never gets initialized.
Also, the reason why it doesn't crash is because:
BYTE *buf = new BYTE(x * y); // allocates a single byte, initialized to the value of (x * y)
BYTE *buf = new BYTE[x * y]; // allocates an array of bytes whose size is x * y

R-P-H

@mranger90 said in Save QImage from BYTE buffer segfaults ?:

@R-P-H Of course it's black, the data never gets initialized.
Also, the reason why it doesn't crash is because:
BYTE *buf = new BYTE(x * y); // allocates a single byte, initialized to the value of (x * y)
BYTE *buf = new BYTE[x * y]; // allocates an array of bytes whose size is x * y

I don't quite understand what you're saying to be honest. Where are you saying the issue is ?

mranger90

@R-P-H here is the amended code

// allocates a buffer of imWidth * imHeight bytes, which  depending on the compiler 
// settings will either be initialized to zero, or may contain garbage
BYTE *buf = new BYTE[imWidth * imHeight];

// creates a QImage based on the data in the buffer, 
QImage img(buf, imWidth, imHeight, QImage::Format_Grayscale8);

// saves the data
img.save("image.bmp", "BMP");
delete [] buf;

The point is that you never put actual image data into the buffer.