I have been using SimpleOpenNI, a wrapper for Processing, all summer now. I use it for the Kinect to make games and demos. Last week, I have been getting a fatal error in my processing window and none of the SimpleOpenNI projects will work. Here is the error:
SimpleOpenNI Version 0.20
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72e8f955, pid=4596, tid=4624
JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
Problematic frame:
C [OpenNI.dll+0xf955]
An error report file with more information is saved as:
C:\Users\mss042\Desktop\processing-1.5.1\hs_err_pid4596.log
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
It appears as if the new OpenNI/NITE/SensorKinect drivers do not work with the SimpleOpenNI wrapper. I have tried it with people using the old drivers and everything still works. Problem is, you cannot download the old drivers off of the websites so I cannot test if it's that or not. You can see everything I've downloaded from the simpleopenni site: http://code.google.com/p/simple-openni/
Any help with this error would be appreciated. Thanks.
Mike
It looks like there's a problem with OpenNI.dll. Make sure that:
You have the dll (It should be in Program Files where you've installed OpenNI)
Make sure you've got the Environment Variables for the Open NI paths and that the paths are correct, otherwise, you might have the .dll file, but the .jnilib wouldn't know where it is.
Had a Kinect Workshop in Uni, and my colleagues using Windows all had issues with the drivers,
so I'm just passing on what they did:
Even though they had 64-bit versions of Windows they used the 32-bit version, and used Brekel OpenNI Kinect Auto Installer - Developer Edition v1.3.2.3.exe(direct link via developkinect.com) after reading this message:
Comment 4 by tijmenva...#gmail.com, Oct 21, 2011 Hey all I have Solved
the unsatisfied link dll error on windows 7 64 bits by installing java
runtime (jre-7u1-windows-i586.exe)and (Brekel OpenNI Kinect Auto
Installer - Developer Edition v1.3.2.3.exe) I uninstalled everything
and than it worked :)
hope this helpes
in Issue#17 on the SimpleOpenNI project issues page.
Another colleague used Synapse and OSC in Processing instead of SimpleOpenNI, but she had loads of errors with the drivers (basically spent a few good hours uninstalling/installing different versions). In her case, uninstalling any previous partial or complete drivers from the machine and deleting any registry entries related to PrimeSense(Sensor, Nite) and OpenNI, then using the installers from the links on the Synapse page, worked for her.
HTH
This is a long shot, but that exact error is also given if the Kinect USB and/or power supply simply becomes unplugged. Thought it was worth mentioning as it is not obvious from the error message itself and it may help someone out if they kicked their power supply and started searching for the above exception :)
Related
I've been having issues opening Arcgis pro for a few days. I've tried all the options provided by the ESRI help team and nothing has worked so far. I have set the TLS 1.2 requirement, the organization and group permissions, added it to trusted sites on my anti virus, etc. I have uninstalled and reinstalled ArcGIS pro and it didn't work. I uninstalled a few programs I though were redundant on my system and suspect that I may have touched once of its dependencies. I uninstalled a version of conda, visual studio, and I suspect a version of python too. This was all in a bid to get arcpy working on this system as the import arcpy command through python IDLE and Pycharm came back with errors. I still have other versions on the system but still can't load Arcgis pro. The help team reached out last 24 hours ago as this error is unusual.
Do you have any ideas on how to get my pro working again please?
I had been using Platform-IO up to 2019 but when I reopened a project things started getting worse and worse. Tasks disappeared and it took a while to be able to compile again. Now Platform-IO has disappeared completely and I was getting deprecation warnings in the "Toggle developer tool' console.
Now after a complete reinstall of VS, Platform-IO etc. the IDE is still not functioning and I regret ever using it. It is like you jump into your car begging it to start. For professional use (able to restart your car every day without a mechanics) this solution needed to be solid and reliable which it does not seem to be. I will have to switch to another IDE I guess. The name Microsoft should have make me hesitate ...
I am using Windows 7 Professional and NO I WILL NOT UPGRADE THE OS.
Is there any means to install a functioning VS-Code / Platform-IO on Windows 7 or is it just an idea of an IDE ?
Sorry to appear mean but "Making you more productive" sounds like a scorn.
I recently tried installing Platform IO on a Win 7 PC of a colleague and experienced similar issues like you. Seems like current Platform IO versions / builds are not compatible and therefore not runnable on Windows 7.
Only idea comes to my mind is using legacy / previous releases of VS Code and Platform IO (manual plugin installation with a legacy release) to get a runnable environment on Win 7, but I didn't test it since I ended up installing a recent Ubuntu next to Win 7. (Seemed like a better solution to me).
Here you can find all of the older releases of VS Code & Platform IO:
https://code.visualstudio.com/docs/supporting/faq#_previous-release-versions
https://code.visualstudio.com/updates/v1_64
https://github.com/platformio/platformio-core/releases
Good luck ;)
jvm terminated exit code 8096 is shown
here follows my eclipse.ini coding
-vm
C:\Program Files (x86)\IBM\SDP70\jdk\jre\bin\javaw.exe
-vmargs
-Xquickstart
-Xms512m
-Xmx1024ms
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:singleJVM,keep
-Xnolinenumbers
-XX:MaxPermSize=1024M
-Dsun.java2d.d3d=false
-Dsun.java2d.noddraw=true
This behavior might be caused by the incorrect rendering on a small set of Microsoft Windows computers with bad DirectDraw or Direct3D drivers. Hence, the use of DirectDraw or Direct3D drivers by Java 2D system in Rational Application Developer v7 can cause the crash.
Note: This error is not always caused as the result of DirectDraw or Direct3D drivers.
Resolving the problem
Consider upgrading to the latest Rational Application Developer v7.0.x release before carrying out the option of disabling Direct3D.
In the case of Rational Application Developer v8.0 or later versions on a Windows 64-bit platform experiencing this JVM error, consult the technote "Internet Explorer v9 or higher is required if the product was installed using the 64-bit Bit Mode option on a 64-bit system". This addresses the jscript.dll error showing in a javacore.
You can also try clearing the temp folder as described in the following forum post. The workaround presented is for Lotus Notes, but may also apply in this case.
WORKAROUND:
To turn off the use of Direct3D in Rational Application Developer v7, you can use the following Java parameter option:
-Dsun.java2d.d3d=false
If that does not solve the problems, try removing DirectDraw or Direct3D completely using:
-Dsun.java2d.noddraw=true
Note: You can put this Java parameter option inside the eclipse.ini in the directory \SDP70\
Open a service request with IBM support if none of the suggestions above have helped to resolve the problem.
Reference Click Here
I have written a program in VB.Net and run it for a few years on Vista and Win 7 without issue. It is a requirements management tool front end to an Access or SQLServer backend database.
A few months ago I installed it on Win 8. It is a 64-bit version of my program running on a 64-bit laptop. It installs fine and runs OK initially. However, after a few weeks it stops running. This has happened twice, the last time after 28 days.
When I try to run the program nothing happens - no splash screen, no error message, no entry in the Applications Log in Event Viewer - just nothing happens. The only solution has been to re-install the program and then it starts working again.
I have tried: turning off all malware, firewall and anti-virus programs; running the program as Administrator; running in various compatibility modes. Nothing happens.
I also tried removing the license file from the program directory. When I did that I did get an error message in the Application Log in Event Viewer, so the program is trying to start. But when I returned the license file it still won't start and there is no error message in the log file.
Program was written in VS 2008 under .Net framework 3.5. I don't think this is an issue, since it runs fine for about a month after install. Also, it is not the license file. The license is perpetual, and anyway if it fails the license there is a splash screen that comes up, and that is not happening.
Can anyone suggest where I might look in Win 8 to try and work out what is going on when I try to start the program?
UPDATE: Through using the Reliability Monitor I have just noticed that at 2:30pm on the afternoon of the problem Windows Installer reconfigured my application. I had the app open all afternoon. but when I shut it at around 4:40pm, then tried to open it again, the problem above emerged.
Description
Windows Installer reconfigured the product. Product Name: Capability Architect. Product Version: 1.0.0. Product Language: 1033. Manufacturer: SDG. Reconfiguration success or error status: 0.
The reason for the reconfiguration was:
Detection of product '{221672D4-9B64-4550-8B8A-A13C4BE20780}', feature 'DefaultFeature', component '{4F120286-6AE1-5DFE-65E4-A4495CA3F296}' failed. The resource 'C:\Users\Public\Desktop\SDG\Capbility Architect Template v2.0.accdb' does not exist.
Now, that file is installed by default with the product. However, I had deleted it earlier that day because I never use it and that seems to have triggered the reconfiguration. Is that normal behaviour?? And why should a reconfiguration stop the program from running? And is it possible to see exactly what the reconfiguration actually did?
EXTRA UPDATE: If this is the problem then I can't replicate it :( I tried deleting the folder again but it has not affected program start up at all.
Thanks
Ian
Hi!
I have an old plugin (as binary, dll), used by my application. It was build for WM2003. And now it crashes the app, if loaded on Windows Mobile 6.1 (WM5 works fine, WM6 too).
The source code is not available and it's no more supported by developer. So I can't rebuild it for WM6.1.
Is it possible to patch or convert the binary to allow it to work on WM6.1 ? If so, how can I do this ?
Thank you.
Edit: I've found, that the problem is in PE loader, which acts not the same on WM6.1 (comparing with WM6 and earlier).
Does this plug-in use MFC or ATL? Earlier versions of WinMo had a different ATL/MFC version baked in, so MFC or ATL apps written in Studio will not work unless you deploy the newer ATL/MFC libraries along with the app, just as the old apps will not work on new devices unless you deploy the old MFC/ATL libraries.
This problem is rare, but some information can be found.
The common solution is to rebuild a binary in VS2008 (TCPMP new VS2008 builds for WM6.1), but this will not help, if you don't have the source code.
I've found the problem explanation and another solution in cegcc mailing list (arm-wince-cegcc on Windows Mobile 6.1). In Windows Mobile 6.1 Memory Management scheme was changes.
This slot arrangement remained pretty constant from Windows Mobile 2003 to Windows Mobile 6.0. However, with the release of Windows Mobile 6.1, things were changed to reduce the DLL pressure and to help out in the Device Manager process space.
In Windows Mobile 6.1, the stacks for the device manager are no longer allocated in the processes’ slot. Instead, the operating system uses slot 59, at the top of the Large Memory Area, for the device manager thread stacks. ...
And the workaround for this issue is to declare the DLL in registry (to tell the OS not to load it in high memory).
I don't like this workaround, so I try to find some binary patcher. And found it :)
It's not really a patcher, it's UPX - the Ultimate Packer for eXecutables. But it solves the problem perfectly. The DLL, packed with UPX don't crashes the application and runs fine.