Beewe
Program hanging when returning from frame()
Hi Beewe,
I am running your windows version in vs 2015, it gets compiled ok, but when I run the program in monocular mode( either mono_kitti or mono_tum), it always hangs forever when returning from calling mCurrentFrame = Frame(mImGray,timestamp,mpIniORBextractor,mpORBVocabulary,mK,mDistCoef,mbf,mThDepth). I stepped into frame function, it successfully returned to where it was called, then when I stepped into the next line of code, the program just hang there forever. The debugger doesn't say anything wrong.
Have you ever had this problem? Do you have any idea why this happens? Thanks!
@ClarityNo1 , I met the same error when running debug solution(the program works well when running release solution), and before its hanging，I got an opengl error output message. I solved it by renaming my dbow2_d.dll(from the folder of debug) to dbow2.dll instead of using dbow2.dll from the folder of release. But another error appeared , the program can not really run untill the end because of "vector subscript out of range". I am struggling to solve the bug.
@huangju91 Thanks very much for your reply! I tried to run it in release mode, and it works great! I didn't get any error output message in debug mode, the program just hangs there without using much CPU. If I comment the line calling frame(), then it can run in debug mode, of course it won't give correct result. I looked online one place says in this situation the problem is mostly caused by using mixed libraries, but I don't know how to find it.
@ClarityNo1 Be sure you use the correct dll. If it‘s not because of dll type，I have no idea what is wrong，either. For my pangolin error, maybe we used different Pangolin versions ,would you share your pangolin links?
@huangju91 Thanks， I will double check the dlls. For pangolin, I just used the link on this page. BTW: I am using opencv3.1, VS 2015 community in Windows 10. I also have the Nvidia 1080 installed before I dived into this project, don't know if it has something to do with opengl.
@huangju91 were you able to solve the "vector subscript out of range" error?
