![]() We have repeated the same procedure with no errors, so this issue seems to be sporadic and, to our knowledge, completely unpredictable. Other than this problem PixInsight runs very well on the same machine. We have to investigate this problem further, but it seems to be an incompatibility of recent NVIDIA graphics drivers for Windows with the versions of Qt used by PixInsight 1.8.6 and later (Qt 5.12.2, 5.12.5 and 5.13.2). The access violation does not happen in our code. I am very sorry to say that we currently have no solution to this problem. ![]() ![]() The access violation error has happened during execution of a long WBPP task with 120 CFA light frames. Today we have been able to reproduce this same problem on a Dell laptop with an NVIDIA graphics card running Windows 10 Pro (see attached screenshot). Sorry for not having more constructive advice to offer. This is more or less what we call normal working conditions. Perform a minimal software configuration that you always should keep as pure as possible. Make sure you install up-to-date device drivers. Please don't install a vendor provided copy of Windows, but an original copy downloaded directly from Microsoft servers. Windows is intrinsically a problematic platform, mainly because of bad design principles, the vast variety of uncontrolled interactions between software and hardware components, the proliferation of malware and bloatware, and also, unfortunately, because of problematic and even buggy system updates.Īssuming the obvious fact that you want to continue using Windows, my only recommendation in such a situation is a complete, clean reinstall of Windows 10. ![]() The kind of issues you are reporting are most likely being caused by hardware-specific conditions, faulty device drivers, wrong operating system components, or conflicts with installed software utilities running as background processes. Unfortunately, If I can't reproduce a nontrivial problem, I am unable to understand and fix it. is stable under normal working conditions on all supported platforms. In all of our tests, which include severe stress tests with many gigabytes of data, version 1. However, none of the issues you are reporting can be reproduced under normal working conditions on a variety of Linux distributions and desktops, macOS 10.11, 10.12 and 10.14, and Windows 10. I am very sorry to know that PixInsight 1.8.6 is performing so badly for you. how we can help - but i know i paid a lot of money for pix and I'd like to keep using it and helping create a better product - what can we do to help find the error? I say that from experience as I am both an Agile Certified Practioner and software development project manager. Just because your machine does not have the issue doesn't mean there isnt one - theres enough of us who do seems to now have issues since 1.8.8 to suggest something a little more than 'bad drivers' There is a problem - now how can we help find the cause it we can't find the log info - windows does not report the error and it appears in diff ways and prob an edge case but theres enough it now makes 1.8.8 unusuable for me so much I have now reverted on machine back to 1.8.5Īnd its not just on here there are issues - people on the pixinsight for beginners FB also report it the same memory errors No pattern - only root cause 1.8.8 - I know its clearly not everyone. other times its at actually writing a file This is something that went in with 1.8.8 - where these memory errors started - last crash for me was star aligning in WBPPP - previous crashed at debayer. dual cpu 48 core 3ghz xeon and 512GB ram so its not related to loading of images into memory and running out. My server can handle anything pix can ever offer it. it leaves no trace in the log but windows throws the memory error There is no pattern - its happened during WBPP at differing times/steps. I have also suffered locked and crashed pixinsight during processing apart from image integration in the latest weeks Now you have multiple people reporting the same memory errors across a variety of PC's - the common issue. all have the latest drivers for their cards and until 1.8.8 NEVER had an issue with pix but simply blaming these issues on windows 10, drivers or memory are not going to helpīoth my machines have far more ram than needed and my server in fact as 512GB of ram so its not the issueīoth machines are opengl 4.5 and all up to date.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |