Things like this are very very very unlikely to be hardware issues. Possibly GPU software issues, but again unlikely (the Khronos libraries all pass the comprehensive khronos test cases). They are almost always software problems at the user end.pawelduda wrote:Hello
I have explained what happens in readme.md of ajstark's OpenVG implementation fork here:
The problem is, I have wasted countless hours on this issue which really slows down the development of my program. Sometimes it crashes after 10 minutes, the other times after 40 minutes. I don't think I have ever gotten with the program running without crash for longer than 90 minutes. The problem is, the final program is expected to run all day.
Would there be a kind soul with the B+ model who could clone the repository and test it on his/her Raspberry Pi? That way I could decide whether it's a hardware or software problem. I made it so that setup process is as minimal as I could.
Could you post the part of code inside the loop? As far as I remember, the issue was closed but I'm not sure if API update has been released to address it. After avoiding code that caused this to happen my software has been running flawlessly for months of uptime.SteveA wrote:I have the same or similar problems to those as described here. I use RP2B with the latest OS and firmware updates and the latest openvg-master (as at 2-9-15). After about 90 mins, the screen gets currupted, fonts are drawn incorrectly and in addition, when I quit my application (with the necessary finish() as described in the documentation) the desktop size has reduced by a slight amount. I have to reboot to get everything back to normal.
If I run my program for say 10 mins then quit, then restart then quit again after 10 mins, and so on all day, all is well. However if I leave the program running (which is just a graphics display loop consisting of rect/line/prompts drawn on the screen) it eventually corrupts.
I saw the post by paweldu Feb 21 which helpfully points to the cause of the issues at https://github.com/ajstarks/openvg/issues/22 and I see that the latest version of openvg-master has got all of the fixes done and that post has been closed, however, my fault still persists and I do not know how to cure it. I am using the latest versions and it is only when it is left running for a long time that a fault develops and nothing in the loop changes.
If anyone has found an actual fix I could really do with some help because my application has to run all day without any corruption.
Thanks for looking
Users browsing this forum: No registered users and 1 guest