Invalid parameter passed to C runtime function
-
Main memory.
the new function can trow that error if you try to allocate and there is not enough free. -
@Lasith
Check your calls to "std::alloc", i.e. everywhere you allocate memory. If you do inadvertently do something which boils down to, say:size_t size = (size_t) -1; std::alloc(size);then you will have memory problems :)
wrote on 9 Nov 2017, 12:00 last edited by@JNBarchan I already have this issue :O
-
Main memory.
the new function can trow that error if you try to allocate and there is not enough free. -
Lifetime Qt Championwrote on 9 Nov 2017, 16:06 last edited by mrjj 11 Sept 2017, 16:10
@Lasith
Add more memory to the pc.
But how much does the target currently have ?
Did you check the how much app uses etc?Or find out if you are leaking memory and hence it runs dry.
You have to find out what causes it using the debugger.
Step through the code to find out where or in what context the
error comes.You have not shown any code so its not possible to guess at.
-
@Lasith
Add more memory to the pc.
But how much does the target currently have ?
Did you check the how much app uses etc?Or find out if you are leaking memory and hence it runs dry.
You have to find out what causes it using the debugger.
Step through the code to find out where or in what context the
error comes.You have not shown any code so its not possible to guess at.
-
@Lasith
Yes it can give a good hint. Start app and see how much it uses.there is also
https://docs.microsoft.com/en-us/sysinternals/downloads/rammap -
Does error comes as soon as you start the app or
does it take some time? -
@mrjj The error oocurs when I click a button which feeds a set of values to a QStringList through 2 for loops!
@Lasith
Ok, you might copy a lot around and run out of memory.
is it 32/64 bit app?
how much memory do you have? -
@Lasith
Ok, you might copy a lot around and run out of memory.
is it 32/64 bit app?
how much memory do you have? -
@mrjj I can not check now :( Its in my office PC Now I am home I will notify you tomorrow! :)
@Lasith
Ok, if you copy lists, it might be the reason.
You should show the code.
Using all mem with strings, takes a lot of strings :) -
@mrjj The error oocurs when I click a button which feeds a set of values to a QStringList through 2 for loops!
wrote on 9 Nov 2017, 16:31 last edited by@Lasith said in Invalid parameter passed to C runtime function:
@mrjj The error oocurs when I click a button which feeds a set of values to a QStringList through 2 for loops!
And you're sure those 2 loops aren't actually unlimited? ;-) Better look at how many iterations they do :) You do have to do really quite a lot of iterations to run out of memory!
-
@Lasith said in Invalid parameter passed to C runtime function:
@mrjj The error oocurs when I click a button which feeds a set of values to a QStringList through 2 for loops!
And you're sure those 2 loops aren't actually unlimited? ;-) Better look at how many iterations they do :) You do have to do really quite a lot of iterations to run out of memory!
wrote on 9 Nov 2017, 16:40 last edited by Lasith 11 Sept 2017, 16:40@JNBarchan No the upper limits of the conditions is finite! Any way I will check and see! Plus if its an infinite loop the error message is different as I remember!
-
@JNBarchan No the upper limits of the conditions is finite! Any way I will check and see! Plus if its an infinite loop the error message is different as I remember!
wrote on 9 Nov 2017, 16:42 last edited by JonB 11 Sept 2017, 16:43@Lasith said in Invalid parameter passed to C runtime function:
@JNBarchan No the upper limits of the conditions is finite!
This is good to know. But there are finite numbers and then there are other finite numbers. Numbers like, say, 0x7FFFFFFF (2 billion?) as the limit in each loop (I'm understanding they are nested?) will cause a lot of iterations... ;-)
-
@Lasith said in Invalid parameter passed to C runtime function:
@JNBarchan No the upper limits of the conditions is finite!
This is good to know. But there are finite numbers and then there are other finite numbers. Numbers like, say, 0x7FFFFFFF (2 billion?) as the limit in each loop (I'm understanding they are nested?) will cause a lot of iterations... ;-)
wrote on 9 Nov 2017, 16:54 last edited by@JNBarchan yeah they are nested for loops!
14/19