App crashes due to QNetworkReply

[Pl45m4]

@Padawan

As the screenshot shows, you have a segfault here. Probably from accessing any invalid pointer.
You commented some lines?! Does it still crash when you run it like this?

For example; I've noticed that you deleteLater your apiData, but there is also a delete apiData in d'tor (commented but still there).

[JoeCFD]

You need to initialize all variables as well, especially on Windows.
QNetworkAccessManager *manager{};
//QNetworkReply *pasteData{};
//QNetworkReply *apiData{};

[Christian Ehrlicher]

@JoeCFD said in App crashes due to QNetworkReply:

especially on Windows.

This is wrong - you always have to initialize your variables...

[JoeCFD]

@Christian-Ehrlicher On Linux the default value is nullptr. It is a good habit to initialize them with nullptr all the time.

[Christian Ehrlicher]

@JoeCFD said in App crashes due to QNetworkReply:

On Linux the default value is nullptr.

No, it is not.

[JoeCFD]

@Christian-Ehrlicher
double * aaa;
std::cout << "aaa=" << aaa << std::endl;
aaa=0

[Christian Ehrlicher]

Just because it does print 0 here it does not mean it's correctly initialized - it's by accident because your stack where aaa points to is currently filled with zeros. A good memory analyzer like e.g. valgrind will tell you that you're accessing uninitialized data.

See https://godbolt.org/z/9vsrva15a - myPtr is not initialized anywhere before usage.

[KroMignon]

@JoeCFD said in App crashes due to QNetworkReply:

double * aaa;
std::cout << "aaa=" << aaa << std::endl;
aaa=0

This is the best way to create an application with random crashes!
Never use a uninitialized pointer.

This is a very basic rule in C/C++.

[JoeCFD]

@KroMignon I know. I always initialize all pointers.

[JoeCFD]

@Christian-Ehrlicher You are right. I tried it in middle of my app and uninitialized pointers are dangled. My memory is getting worse. I remember one of the differences between Linux and Windows is that variables on Linux have default values. I am wrong. But I do initialize all my pointers.

[JonB]

@JoeCFD
It's a C++ language thing, so not per-platform. What you may find, on any platform/compiler, is that there is a difference between what you find in uninitialized (stack) variables between debug versus release builds. Or that may apply to heap areas. It's all undefined :)

[KroMignon]

@JoeCFD said in App crashes due to QNetworkReply:

I remember one of the differences between Linux and Windows is that variables on Linux have default values. I am wrong. But I do initialize all my pointers.

AFAIK, on Linux/GCC pointers are never initialized per default.
On Windows/MSVC, they are set to 0 in debug build, but not in release.

[JoeCFD]

@KroMignon Good to know. Thanks. I have not followed this for ages.

[Christian Ehrlicher]

@KroMignon said in App crashes due to QNetworkReply:

On Windows/MSVC, they are set to 0 in debug build, but not in release.

Wrong again - it's 0xCCCCCCCC or 0xCDCDCDCD
See https://en.wikipedia.org/wiki/Magic_number_(programming)#Debug_values

[KroMignon]

@Christian-Ehrlicher said in App crashes due to QNetworkReply:

Wrong again - it's 0xCCCCCCCC or 0xCDCDCDCD

Yes, I was wrong... sorry, too fare away.
I mixed up pointer initialization and variable initialization!!

[Padawan]

@Pl45m4 It always crashes if the API Key Request process happens