QThread::start: Failed to create thread (The access code is invalid.) terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc

Dunant · wrote on 26 Apr 2021, 03:39

Dear All,

i am having program crashed with message :

QThread::start: Failed to create thread (The access code is invalid.)
terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information

Please kindly advise me, is it caused by Operating System Windows 2016 (that i am using) or caused by the QT Compiler not compatible or coding issue ?

thank you for your kind attention.

best regards,
dunant

Christian Ehrlicher · 26 Apr 2021, 05:09

Use a debugger, take a look at the backtrace where it crashes and why.

Dunant · wrote on 26 Apr 2021, 05:09

@Christian-Ehrlicher : actually i am the end-user of the application. My developer said it is caused by my server's Operating System Windows 2016 that causee his program crashed and displaying the messages i mentioned above

Christian Ehrlicher · 26 Apr 2021, 05:32

But what should we do against this then?

Dunant · wrote on 26 Apr 2021, 05:32

@Christian-Ehrlicher : if from your view, based on your long experiences, may i know is it caused by Operating System Windows 2016 (that i am using) or caused by the QT Compiler not compatible or coding issue ?

Christian Ehrlicher · 26 Apr 2021, 05:44

It can be all of them. Since Windows Server 2016 is based on Win10 I doubt it's an OS issue. The only way to find it out is to debug the crash.

Dunant · wrote on 26 Apr 2021, 05:44

@Christian-Ehrlicher : oh i see, many many thanks for your view and feedback , really appreciated. Let me once again check with them. By the way, anybody here in the Forum feel free to give your feedback or comments, thank you for all your kind attention

SGaist · 27 Apr 2021, 00:56

Hi,

In addition to @Christian-Ehrlicher, are you running a 32 or 64bit version of the OS ? What about the application ?

One of the reasons for that error to be thrown is memory exhaustion but it's not the only one. See here.

Dunant · 13 Sept 2021, 15:07

@SGaist : oh, i am running Windows Server 2016 64-bit, let me attached the screen capture for your view :

Dunant · D Dunant 27 Apr 2021, 00:56

@SGaist , the application built in 64bit. The Windows Server 2016 is 64bit

SGaist · 14 Sept 2021, 09:39

Did you check your RAM hardware health ?

Dunant · 14 Sept 2021, 10:09

@SGaist , the RAM is 16 GB, the available /free RAM still 13,4 GB

JonB · 16 Sept 2021, 02:54

@Dunant
I don't think @SGaist [please correct me if I have misinterpreted] is asking you to report how much RAM you have, he is asking to "check your RAM hardware health". I read that as run a physical hardware memory checker. I don't know why he suspects that from the output you showed, but he usually knows what he is talking about....

Dunant · J JonB 14 Sept 2021, 10:09

@JonB the RAM hardware health is good, based on my visual monitoring

Dunant · 11 Jan 2021, 07:35

since 29 March 2021 until today (already 7 months), the application not crashing anymore due to every midnight i did restart the operating system Windows Server 2016.
Today i just had meeting with our vendor, the vendor still saying nothing wrong with the application , not admitting their application that caused the crash problem, and blame our server's operating system that having problem. I am not programmer/developer so i have nothing to say. At the end of the discussion, our vendor informing us to use Linux Red Hat operating system which they claimed no issue. I will discuss internally about this.