when I run this tutorial https://www.tensorflow.org/lite/tutorials/model_maker_object_detection
on a GPU I get the following error: "Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above."
I do not have any warning log messages printed above the error message.
No issues if I run on a CPU.
I do not make any changes to the tutorial before execution.
Searching online I found that the problem may disappear if I reset the runtime. It does not work for me.
Searching online I found that the problem may be with the version of cuDNN. Before spending time to change the cuDNN version, I would like to know your opinions.
Please let me know if you need further information.
Thanks,
Federico
I am trying to compile the webRTC code but I get the following error.
I am not trying with Visual Studio.
The error got is <PATH>/src/buildtools/win/gn.exe cannot start because of incompatibility of 64 bit windows version. The confusion is I am compiling on Windows 7 64 bit. The error is confusing to say the least.
Steps followed are :-
Unzipping the depot_tools from the chromium webpage and setting up the correct path.
Then for downloading the webRTC and compilation the steps were
mkdir webrtc-checkout
cd webrtc-checkout
fetch --nohooks webrtc
gclient sync
gn gen out/Default < The problem arises here >
We would need the entire trace of all the python script to give you a full answer, but it is VERY likely that you need to have MSVC 2015 (14) installed and to set the corresponding environment variable DEPOT_TOOLS_WIN_TOOLCHAIN=0. The scripts will otherwise stop working with cryptic error messages, even before the compilation. It fits your "symptoms".
See this for more answers (chromium and webrtc build instructions are shared):
https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
If you copy paste the trace form the python scripts here, I might be able to help you more.
I am currently running a VB application through mono on Raspbian. After a bit of troubleshooting the program boots and appears to be running quite well. However if left to itself for a few minutes the VB application just shuts off. This program runs excellently on the windows pc for any duration. Barring this being an issue with the VB code itself is there any major PI related issues that I may have missed in setting up mono? I set up mono the usual way and am launching via "sudo mono app.exe" in terminal.
Thank you for any insight you may provide into this!
UPDATE: mono just FINALLY threw out an errot to me System.OutOfMemoryException : Not enough memory to complete operation [GDI+ status: out of memory]
UPDATE2: Memory leak, its a code related issue.
Hi to anyone else that runs into this issue. For us it was a memory leak.
I m having trouble with AIR debug launcher(adl) under win 7 64 bits home familial with AIR SDK runtime 2.7. It sometimes crash and i have no posibilities to understand if its because of my software or not.
Does anybody know how I can get some logs to know why it crashed ?
When its crash, the debugger is going away and i dont know where my software bugged if it did...
I have been testing my software under different SDK under win7 and i still had some adl crash. The software is working correctly under winXP. I suppose it has something to do with win7 and AIR but how can I find any informations on what is going on...?
thanks for any tips...
i have been able to find windows crash dump files. Then i have download windbg. And started debugging air debugger launcher... but im stuck... not good debugging without symbol files... I guess cant do more then that. The error come from an attempt to convert an integer to a unicode string but i dont know why this function is called, by who and when...
sometimes it doesnt crash also.
Finally found some windows crash dump log files. Also started to debug with windbg the AIR. :))) lol
I'm new to MonoTouch and more times than not, when I try to run my MonoTouch app on the iPhone simulator (debug mode and regular), I receive a long error output that begins with the following message:
Error connecting stdout and stderr (127.0.0.1:10001)
Couldn't register com.yourcompany.[appnamehere] with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.Stacktrace:
at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <0x00004>
at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <0x00004>
at MonoTouch.UIKit.UIApplication.Main (string[],string,string) <0x00089>
at MonoTouch.UIKit.UIApplication.Main (string[]) <0x00014>
at PodcastManager.Application.Main (string[]) <0x00010>
at (wrapper runtime-invoke) .runtime_invoke_void_object (object,intptr,intptr,intptr) <0x00043>
And ends with:
=================================================================
Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application.
=================================================================
The weird thing is it will work some of the time. Once, a reboot of my machine did it. Others, just restarting MonoDevelop and/or the simulator.
I can provide the entire error output if you think that may help.
Any ideas?
This is a problem with the monotouch debugger. Sometimes, when the application crashes, the debugger hangs in memory, and that then prevents you from running the app again. As you said, sometimes closing MonoDevelop and the simulator is enough to clean up the debugger, sometimes you need a full reboot. This is also the experience I have, which is probably the only bad thing I found with monotouch so far.
Many times, I'm able to directly kill the process from the console. To do that, open the console and type "top". You'll see the list of processes using the most memory, your app will likely be on top, using almost 100% of cpu. Save the id of the that line, and type q to quit. Now type "kill -9 ???" where ??? is the id you got from top.
Monotouch 2.0 fixed a lot of these problems, if you haven't updated yet I would seriously recommend you to do so. I'm running the beta channel of 2.0, and its a LOT more stable. Crashes went down from 1 or 2 every hour to 1 or 2 a day. It still happens, though, unfortunately.
-- Update -- after updating to 2.0.2 I have not seen this issue.
After playing with it long enough, and coming across this bug report I've come to the conclusion that until it's fixed the way to prevent this error is by NEVER stopping a debug session in the IDE. As long as you stop the debug session when the code is not at a breakpoint by hitting the home button it appears that you will avoid this situation.
I think this error comes when any native library of monotouch is missing. It happen due to uninstall Visual Studio or Update Xamarin. I faced the Same error and resolve it by Unistalland reinstall the Xamarin Visual Studio and Xamarin Studio. It takes 10 min and all issues are solved.