Issue with threading and opencv
-
-
-
@jsulm : This is the only thing which i see after crash with exception triggered.
Is there any other way to do so@Kira In QtCreator if you start with debugger you will have a stack trace
-
@Kira Yes. Now you need to go from top to bottom until you hit first source code file from your project and check it at the line mentioned in the stack trace.
-
@Kira Yes. Now you need to go from top to bottom until you hit first source code file from your project and check it at the line mentioned in the stack trace.
wrote on 14 Jun 2019, 10:03 last edited by@jsulm : I tried doing it but the error is expected to come after thread running >150 times which is making the debugging process very difficult.
I have also sample test case on github can you please go through it for any possible issues.
https://github.com/HackersSpirit/ImageProcessor -
@jsulm : I tried doing it but the error is expected to come after thread running >150 times which is making the debugging process very difficult.
I have also sample test case on github can you please go through it for any possible issues.
https://github.com/HackersSpirit/ImageProcessor@Kira said in Issue with threading and opencv:
150 times
you can tell a breakpoint to be ignored for a certain amount of time
-
@jsulm : I tried doing it but the error is expected to come after thread running >150 times which is making the debugging process very difficult.
I have also sample test case on github can you please go through it for any possible issues.
https://github.com/HackersSpirit/ImageProcessor@Kira I actually suggested to go through the stack trace after crash from top to bottom. No break points needed for that.
-
@Kira I actually suggested to go through the stack trace after crash from top to bottom. No break points needed for that.
wrote on 14 Jun 2019, 10:14 last edited by Kira@jsulm :
@Kira said in Issue with threading and opencv:@jsulm : Are you referring to this:
Please let me know in case of any issuesThis is the stack trace which i get posted earlier referring from line no 1. It does not point to line of code where program has a break.
But line 16 and 17 point to the line of the code.
Should i refer those line for particular cause of the program to break
Please do let me know if i getting something wrong -
@jsulm :
@Kira said in Issue with threading and opencv:@jsulm : Are you referring to this:
Please let me know in case of any issuesThis is the stack trace which i get posted earlier referring from line no 1. It does not point to line of code where program has a break.
But line 16 and 17 point to the line of the code.
Should i refer those line for particular cause of the program to break
Please do let me know if i getting something wrong@Kira Check your code in that source code at line 16 and 17.
-
wrote on 14 Jun 2019, 10:34 last edited by
@jsulm :
Line 16 is pointing to following line in bold:
void ImageMapping::requestReWorkNew()
{
cout<<"Inside requestRework Newwwwwwwwww"<<endl;
const int sleep = 50;
int queueSize = queueImageName.size();
cout<<"Queue size Request Rework New: "<<queueSize<<endl;
if(queueImageName.size()!=0){
//Get the current image number from the list of images
mutex.lock();
_working = true;
_abort = false;
mutex.unlock();
cout<<"Emiting resume work"<<endl;
emit resumeWork();
}else{
cout<<"Signalling retrying"<<endl;emit retrying(); }}
This function is basically a slot triggered by following signal:
connect(imageMapping, SIGNAL(finished()), imageMapping, SLOT(requestReWorkNew()));
connect(imageMapping, SIGNAL(retrying()),imageMapping,SLOT(requestReWorkNew())); -
@jsulm :
Line 16 is pointing to following line in bold:
void ImageMapping::requestReWorkNew()
{
cout<<"Inside requestRework Newwwwwwwwww"<<endl;
const int sleep = 50;
int queueSize = queueImageName.size();
cout<<"Queue size Request Rework New: "<<queueSize<<endl;
if(queueImageName.size()!=0){
//Get the current image number from the list of images
mutex.lock();
_working = true;
_abort = false;
mutex.unlock();
cout<<"Emiting resume work"<<endl;
emit resumeWork();
}else{
cout<<"Signalling retrying"<<endl;emit retrying(); }}
This function is basically a slot triggered by following signal:
connect(imageMapping, SIGNAL(finished()), imageMapping, SLOT(requestReWorkNew()));
connect(imageMapping, SIGNAL(retrying()),imageMapping,SLOT(requestReWorkNew()));@Kira Are you sure this is the line? The actual line is mentioned in the "Line" column in the stack trace. So, it would be 2129.
-
@jsulm :
Line 16 is pointing to following line in bold:
void ImageMapping::requestReWorkNew()
{
cout<<"Inside requestRework Newwwwwwwwww"<<endl;
const int sleep = 50;
int queueSize = queueImageName.size();
cout<<"Queue size Request Rework New: "<<queueSize<<endl;
if(queueImageName.size()!=0){
//Get the current image number from the list of images
mutex.lock();
_working = true;
_abort = false;
mutex.unlock();
cout<<"Emiting resume work"<<endl;
emit resumeWork();
}else{
cout<<"Signalling retrying"<<endl;emit retrying(); }}
This function is basically a slot triggered by following signal:
connect(imageMapping, SIGNAL(finished()), imageMapping, SLOT(requestReWorkNew()));
connect(imageMapping, SIGNAL(retrying()),imageMapping,SLOT(requestReWorkNew()));@Kira you can double click on the line (in QtCreator) of the stack trace and it will open the file at the correct line
-
@Kira Are you sure this is the line? The actual line is mentioned in the "Line" column in the stack trace. So, it would be 2129.
-
@jsulm : Actually i have recreated the issue.the program i am referring now is from github. I have cross checked the line which I highlighted is the same. If u want i can repost the image
-
wrote on 17 Jun 2019, 06:09 last edited by
@J-Hilk @jsulm : Hello guys sorry for the late update i was working on the issue.
Would like to share the update.
I trimmed down the issue further by first commenting out all the cout statements as the logs which
was coming pointed to the ostream file of the cout.
So the call stack pointed out to the opencv file stating unable to save the image.
So i commented the save function to find any thing else was causing the issue. What i found that my program was still breaking and the call stack pointed to the thread function.
I placed a counter for the signal and slot of the thread and it was found that it executed 666 times approx before breaking. -
wrote on 17 Jun 2019, 08:03 last edited by
@J-Hilk
@jsulm :Guys thanks for your support i finally figured where exactly the problem was:
There was issue with the logic which was used for implementation. As you can see the code on github.
Instead of requesting the task in the dowork function every time a signal is raised and an slot is called to execute the task.
This led to the calling of so many signals and slots within a given time that it caused the stack to overflow.
The issue will be resolved by removing the signal slot loop. This issue was top priority, a big learning curve for my future implementations in dealing with signal and slot mechanism.Thanks for your support.
Just one last question which i would like to be answered which triggered with this implementation.- Is there any limitation of how much slots can reside at a given time on a stack?
As per my observation at a given time 666 approx signal/slots calls were made after which the program crashed. - Is the slot entry is cleared or maintained on the stack after the execution and can be increase the size of stack or transfer it to heap?
Regards
- Is there any limitation of how much slots can reside at a given time on a stack?
-
@J-Hilk
@jsulm :Guys thanks for your support i finally figured where exactly the problem was:
There was issue with the logic which was used for implementation. As you can see the code on github.
Instead of requesting the task in the dowork function every time a signal is raised and an slot is called to execute the task.
This led to the calling of so many signals and slots within a given time that it caused the stack to overflow.
The issue will be resolved by removing the signal slot loop. This issue was top priority, a big learning curve for my future implementations in dealing with signal and slot mechanism.Thanks for your support.
Just one last question which i would like to be answered which triggered with this implementation.- Is there any limitation of how much slots can reside at a given time on a stack?
As per my observation at a given time 666 approx signal/slots calls were made after which the program crashed. - Is the slot entry is cleared or maintained on the stack after the execution and can be increase the size of stack or transfer it to heap?
Regards
@Kira 1. Sure but I guess it depends on many factors. You should not rely on it and avoid flooding the signal queue
2. Not sure I understand the question. Which slot entry do you mean? Slots are not put into the signal queue. And the stack is automatically cleared when a function/method (which a slot is) finishes, nothing Qt specific. - Is there any limitation of how much slots can reside at a given time on a stack?
-
@Kira 1. Sure but I guess it depends on many factors. You should not rely on it and avoid flooding the signal queue
2. Not sure I understand the question. Which slot entry do you mean? Slots are not put into the signal queue. And the stack is automatically cleared when a function/method (which a slot is) finishes, nothing Qt specific.wrote on 17 Jun 2019, 08:13 last edited by@jsulm said in Issue with threading and opencv:
@Kira 1. Sure but I guess it depends on many factors. You should not rely on it and avoid flooding the signal queue
2. Not sure I understand the question. Which slot entry do you mean? Slots are not put into the signal queue. And the stack is automatically cleared when a function/method (which a slot is) finishes, nothing Qt specific.- Sorry if not understood i will just try to clear :). Actually i my assumption due to the implementation logic there were so many signals generated that caused the stacks to overflow giving error at different points.
For example sometime i got error at saveImage function. while sometimes at calling the slot etc.
I still need to clarify my assumptions using different test cases but probably this should be the cause why the program crashed.
- Sorry if not understood i will just try to clear :). Actually i my assumption due to the implementation logic there were so many signals generated that caused the stacks to overflow giving error at different points.
-
@jsulm said in Issue with threading and opencv:
@Kira 1. Sure but I guess it depends on many factors. You should not rely on it and avoid flooding the signal queue
2. Not sure I understand the question. Which slot entry do you mean? Slots are not put into the signal queue. And the stack is automatically cleared when a function/method (which a slot is) finishes, nothing Qt specific.- Sorry if not understood i will just try to clear :). Actually i my assumption due to the implementation logic there were so many signals generated that caused the stacks to overflow giving error at different points.
For example sometime i got error at saveImage function. while sometimes at calling the slot etc.
I still need to clarify my assumptions using different test cases but probably this should be the cause why the program crashed.
@Kira said in Issue with threading and opencv:
- Sorry if not understood i will just try to clear :). Actually i my assumption due to the implementation logic there were so many signals generated that caused the stacks to overflow giving error at different points.
For example sometime i got error at saveImage function. while sometimes at calling the slot etc.
I still need to clarify my assumptions using different test cases but probably this should be the cause why the program crashed.
Hi, great that you managed to work it out thumbsUp
Sadly I'm quite a but under time pressure and was unable to take a closer look on your uploaded project :(
To your question.
The (default)stack limit is highly OS depended but In most cases, the max stack size of the main thread is significantly large, that you won't run into issues, even in highly recursive functions.
IIRC, than on an ordinary desktop PCs, the call stack for Windows defaults to 1mb, 8mb for Linux, and 8-64mb for OSXFor 2ndary threads, that can be quite different for macOS, that's reduced to 512 kbyte
- Sorry if not understood i will just try to clear :). Actually i my assumption due to the implementation logic there were so many signals generated that caused the stacks to overflow giving error at different points.
30/41