-
Hi, I want to talk about a problem and ask who to contact. The problem occurs in all binaries of Microsoft OpenJDK, the Intel but also the ARM, 32 and 64 bit. Of course I could get a newer Surface with 3 times faster CPU that emulates the Intel stuff 3 times faster... but that's waste of ressources as the Intel emulations eats up the battery very fast. So ... how to run a diagnostic on what went wrong? Debugview does not show anything I do understand. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
@ojutan - Does Prorealtime interact with native components or spin up a Desktop GUI? Is there a free trial version that we can test with? |
Beta Was this translation helpful? Give feedback.
-
hi, sorry for the late answer... the application builds up a GUI in java, but the way it is paunched prohibits any third party testing. 1.) you need to have a contract with the vendor, for later accessing a third-partie's API. You get access mainly by signing up for a contract, get your ID verified and the account approved... then it downloads the app instaler. Once installed the web page launches the app with encrypted parameters having the account information (real or demo)... I myself cannot look too deep into that software, but my guess is that it initializes its core api until it wants to spawn some child processes to display GUI elements but that never happens. In emulator it comes with several indenendant windows displaying HLOC charts. Here the vendor Prorealtime has no interest to pursue this issue... so this might remain unsolved for a longer time. Maybe it happens in "bypass bugfixing" when other issues are solved. For the time being I am using the not-so-bad web interface which works in Chrome for ARM but not in IE Edge Chromium for ARM... |
Beta Was this translation helpful? Give feedback.
OK, best I can offer is to have Prorealtime contact us and we can try to fix it with them.