WBPP Bug again

[Hrado13]

Processing script file: C:/Program Files/PixInsight/src/scripts/WeightedBatchPreprocessing/WeightedBatchPreprocessing.js
*** Error [000]: C:/Program Files/PixInsight/include/pjsr/NumericControl.jsh, line 153: Error: At address 00007FFB6B926240 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008

[Juan Conejero]

We cannot reproduce this problem on any platform. Unless you can provide a reproducible pattern, this is a machine-specific issue. This is not a bug in the WBPP script.

The most probable cause for this problem on Windows is an outdated or wrong graphics driver, especially an incompatible OpenGL implementation. Check that you have the latest driver version installed for your graphics card. If you are using Windows 7 or Windows 8.x, note that they are not supported by current versions of PixInsight. We only support Windows 10.

[XcalRocketMan]

Interesting.  I've been getting the same error as well, pretty consistently. Tried rebooting my PC, reloading PI. Nothing seems to work. Although I don't think I can see the location of where the error is cropping up. I'll try to get more info later this evening.

[Hrado13]

It Happens only Sporadically....It is not consistent...It just happened again

[greendaleobs]

I can reproduce the same error everytime I run WBPP 1.4.1 and the latest updates to pix

it ran fine before using BPP so something is odd since the last update or 1.4.1 scripts

windows server 2019 std edn ver 1809 29 sept 2019 OS Build 17763.379

[greendaleobs]

see reports of it on FB page pixinsight for beginners too

same error

[greendaleobs]

We cannot reproduce this problem on any platform. Unless you can provide a reproducible pattern, this is a machine-specific issue. This is not a bug in the WBPP script.

The most probable cause for this problem on Windows is an outdated or wrong graphics driver, especially an incompatible OpenGL implementation. Check that you have the latest driver version installed for your graphics card. If you are using Windows 7 or Windows 8.x, note that they are not supported by current versions of PixInsight. We only support Windows 10.

both PC's that have this are running OpenGL 4.6 and are kept up to date - both windows 10

[jpadron]

Hi!

Same error here. Everything is updated. Windows 10 (1909). I don't know how to provide a reproducible pattern because occur whith the same data in different occasions. Don't have any other dataset to play with.

Thanks in advance,
Jorge

[Russ]

This bug is not occurring on my Mac.

[Juan Conejero]

We have just finished a stress test of PixInsight 1.8.8-1 on Windows 10. We have ran it on two different computers:

- An Apple iMac (late 2015 27" model, BOOTCAMP partition): Intel core i7 6800K @ 3.40 GHz, 32 GB of RAM, AMD Radeon R9 M395, 5K Retina display.

- A Dell Precision laptop: Intel Xeon E3 1505M v5 @ 2.80 GHz, 32 GB of RAM, NVIDIA Quadro M1000M + integrated Intel HD Graphics P530, 4K display.

Both machines run Windows 10 Pro with all available updates installed, including graphics drivers. Both machines have McAfee Total Protection installed and fully updated with real-time protection turned on.

The test has lasted 7 hours. It includes several huge projects with a variety of image types, formats and sizes, complex real-time preview sessions, multiscale processes, dynamic processes, several WBPP executions with different sets of 50 and 100 frames, SubframeSelector, ImageIntegration and DrizzleIntegration with the resulting images, astrometric solutions with the ImageSolver script, PhotometricColorCalibration, and AnnotateImage, among other processes and scripts. Most tasks have been repeated at least four times.

Absolutely zero problems. Everything has been executed perfectly by the current PixInsight platform on Windows 10.

Unless somebody can provide a pattern or sequence of operations that allow us to reproduce the problems reported here consistently, they are machine-specific issues.

[jpadron]

Time to buy a new computer then... 

Thanks anyway

[greendaleobs]

Unless somebody can provide a pattern or sequence of operations that allow us to reproduce the problems reported here consistently, they are machine-specific issues.

helpful ....

esp as there are numerous people reporting it ...

this was not an issue until this week when 1.4.1 went in and i got 4 updates at the same time

before that WBPP ran and I never ever had an issue with stability now

I find it hard to understand on 2 machines where it was stable it now isn't and suddenly its machine specific

while it might be an edge case its that error when running WBPP ... never done it before

[Juan Conejero]

During the intensive tests we have carried out today, we have discovered an obscure bug in version 1.8.8-1 of PixInsight that has been causing sporadic segmentation faults during execution of several scripts, including BPP and WBPP. The bug happens during garbage collection (GC) of closed image window objects performed by the JavaScript engine. Since JavaScript's GC is non-deterministic, the bug is difficult to reproduce. Furthermore, it only happens during relatively aggressive GC tasks, which are more likely during very long script executions and/or working with large amounts of data (keep in mind that the garbage collector has a fixed threshold of 4 GiB to start collecting unused objects automatically, so this is independent on the amount of available RAM).

This bug is now fixed in version 1.8.8-2 of the PixInsight core application. We'll release it as a regular update tomorrow. Hopefully this will fix all of these problems during script execution.

[drlzf]

run --execute-mode=auto "C:/Program Files/PixInsight/src/scripts/WeightedBatchPreprocessing/WeightedBatchPreprocessing.js"

Processing script file: C:/Program Files/PixInsight/src/scripts/WeightedBatchPreprocessing/WeightedBatchPreprocessing.js
*** Error [228]: C:/Program Files/PixInsight/src/scripts/WeightedBatchPreprocessing/WeightedBatchPreprocessing-engine.js, line 2723: SyntaxError: JSON.parse: bad control character in string literal