ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-01-12T13:40:55-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22445Wrong error message from `SaveScreenshot` when save directory doesn’t exist2024-01-12T13:40:55-05:00Alankar DuttaWrong error message from `SaveScreenshot` when save directory doesn’t existWhen I use the following line in Python trace, `pvpython` complains that it has run out of disk space when the directory passed doesn’t exist. This is a misleading error message and hopefully straightforward to fix. I don’t know if anyon...When I use the following line in Python trace, `pvpython` complains that it has run out of disk space when the directory passed doesn’t exist. This is a misleading error message and hopefully straightforward to fix. I don’t know if anyone else is also getting this. I just wanted to report it here for developers to take notice.
Discourse thread: [here](https://discourse.paraview.org/t/wrong-error-message-from-savescreenshot-when-save-directory-doesnt-exist/13661/1)
```
SaveScreenshot(f'{screenshot_loc}/screenshot-{file_no:04d}.png', layout1, SaveAllViews=1,
ImageResolution=[1102, 664],
FontScaling='Scale fonts proportionally',
SeparatorWidth=1,
SeparatorColor=[0.937, 0.922, 0.906],
OverrideColorPalette='',
StereoMode='No change',
TransparentBackground=0,
# PNG options
CompressionLevel='0',
MetaData=['Application', 'ParaView'])
```Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22431vtkPProbeFilter issue when first rank doesn't produce data2024-01-12T11:05:15-05:00Berk GevecivtkPProbeFilter issue when first rank doesn't produce dataWhen probing in parallel, if the vtkPProbeFilter does not intersect with the source data on the first rank, the output does not contain any probed data (just the mesh). This is because the filter relies on the list of arrays on the first...When probing in parallel, if the vtkPProbeFilter does not intersect with the source data on the first rank, the output does not contain any probed data (just the mesh). This is because the filter relies on the list of arrays on the first rank to populate the output mesh (which is empty in this case).Berk GeveciBerk Gevecihttps://gitlab.kitware.com/paraview/paraview/-/issues/22442Automate Tutorial tests as part of CI2024-01-11T20:07:50-05:00Spiros TsalikisAutomate Tutorial tests as part of CICreate automated tests out of the Self-Directed and Classroom tutorials on docs.paraview.org, and add them as part of CI.
- https://docs.paraview.org/en/latest/Tutorials/SelfDirectedTutorial/index.html
- https://docs.paraview.org/en/l...Create automated tests out of the Self-Directed and Classroom tutorials on docs.paraview.org, and add them as part of CI.
- https://docs.paraview.org/en/latest/Tutorials/SelfDirectedTutorial/index.html
- https://docs.paraview.org/en/latest/Tutorials/ClassroomTutorials/index.html#
@cory.quammen @ben.boeckel @wascott5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22430Assertion failure when opening ADIOS2 bp files - ParaView built with -Wp,-D_G...2024-01-11T15:22:35-05:00Jakub KlinkovskýAssertion failure when opening ADIOS2 bp files - ParaView built with -Wp,-D_GLIBCXX_ASSERTIONSArch Linux has [ParaView 5.11.2](https://archlinux.org/packages/extra/x86_64/paraview/) built with the `-Wp,-D_GLIBCXX_ASSERTIONS` flag. This leads to an assertion failure in `std::vector::operator[]` when opening an ADIOS2 bp file.
To ...Arch Linux has [ParaView 5.11.2](https://archlinux.org/packages/extra/x86_64/paraview/) built with the `-Wp,-D_GLIBCXX_ASSERTIONS` flag. This leads to an assertion failure in `std::vector::operator[]` when opening an ADIOS2 bp file.
To provide some testing data, compile [test.cpp](/uploads/ac8cd54c5f0f09ad909b61f5e57c07f5/test.cpp) with
g++ -std=c++17 test.cpp -l adios2_cxx11
Then run `./a.out` which creates the `test.bp` directory with synthetic data. Run `paraview`, select _Open_ in the menu and navigate to the `test.bp` directory. Upon opening, Paraview will dump core. I managed to get a full backtrace from `gdb`, the top is
```
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid = <optimized out>
ret = 0
pd = <optimized out>
old_mask = {__val = {0}}
ret = <optimized out>
#1 0x00007ffff7e318a3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#2 0x00007ffff7de1668 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
ret = <optimized out>
#3 0x00007ffff7dc94b8 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, sa_mask = {__val = {140737316447456, 1125, 140737316447272, 0, 0, 0, 0, 0, 0, 93823560581128, 72, 140737353595584, 18446744073709551552, 0, 140737488333448, 93825070916192}}, sa_flags = -136053587, sa_restorer = 0x7ffff0e786e0 <(anonymous namespace)::num_get_c>}
#4 0x00007ffff0cdd3b2 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*)
(file=file@entry=0x7ffff5c0e4e0 "/usr/include/c++/13.2.1/bits/stl_vector.h", line=line@entry=1125, function=function@entry=0x7ffff5c0e428 "std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = int; _Alloc = std::allocator<int>; reference = int&; size_type = long unsigned int]", condition=condition@entry=0x7ffff5c0a246 "__n < this->size()") at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/debug.cc:61
#5 0x00007ffff5af0070 in std::vector<int, std::allocator<int> >::operator[](unsigned long) (__n=0, this=<optimized out>, this=<optimized out>, __n=<optimized out>)
at /usr/include/c++/13.2.1/bits/stl_vector.h:1125
number_of_elements = 0
number_of_elements_per_command = 0
elementTypesStrMap = std::map with 3 elements = {["double"] = 1, ["int"] = 0, ["str"] = 2}
values = Python Exception <class 'OverflowError'>: int too big to convert
Python Exception <class 'OverflowError'>: int too big to convert
Python Exception <class 'OverflowError'>: int too big to convert
{<std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >> = std::vector of length -4250937, capacity -1466013161515 = {"fH", "\000\000\000\000\005\000\000\000\360f\000ZUU", '\000' <repeats 18 times>, " \362\005ZUU\000\000\006\000\000\000\000\000\000\000double\000\000\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\201", '\000' <repeats 11 times>, "PU\000\000\0004\006ZUU", '\000' <repeats 18 times>, "[#\000\000UU\000\000x\v\310\365\377\177", '\000' <repeats 18 times>, "\020\000\006\000\000\000\000\000\300P\343YUU\000\000\003\000\000\000\000\000\000\000[#\000\000\000\000\000\000\002", '\000' <repeats 23 times>..., <error reading variable: Cannot create a lazy string with address 0x0, and a non-zero length.>, <error reading variable: Cannot create a lazy string with address 0x0, and a non-zero length.>, <error reading variable: Cannot create a lazy string with address 0x0, and a non-zero length.>, <error: Cannot access memory at address 0x3>, "double", "", "H\211", " x?\366\377\177\000\000\001", '\000' <repeats 23 times>, "\362\020\001", '\000' <repeats 13 times>, "\240\344\372VUU", '\000' <repeats 26 times>, "\340\344\372VUU\000\000P\345\372VUU\000\0000\350\372VUU\000\000\220\267\371VUU\000\000\000\000\000\000\000\000\000\000q\000\000\000\000\000\000\000\360\345\372VUU\000\000\360\346\372VUU\000\000\360\346\372VUU\000\000\000\347\372VUU\000\000\000\350\372VUU\000\000\000\350\372VUU\000\000@\352\372VUU\000\000H\352\372VUU\000\000H\352\372VUU\000\000"..., "", "\036\000\000\000\000\000\000\000\224\360\343\367\377\177\000\000P\254\377\377\377\177\000\000\f\000\000\000\000\000\000\000DataSourceIO\000\377\377\377p\254\377\377\377\177", '\000' <repeats 18 times>, "\002\000\000\000\000\000\000\000@\025\347\360\377\177\000\000\330\033\347\360\377\177\000\000P\231\002ZUU\000\000P\231\002ZUU\000\000P\231\002ZUU\000\000@\231\002ZUU\000\000Z\231\002ZUU\000\000@\233\002ZUU\000\000 \215\347\360\377\177\000\000\020\000\000\000\377\177\000\000@\231\002ZUU\000\000\020\000\000\000\000\000\000\000\000\002\000\000\000\000\000\000ingVect\000p\323\346\360\377\177\000\000"..., "", "H\213L$\bH\203\371\037\017\206%\001\000\000H\213EpfI\017n\347I\215T\035\000fH\017n\300f\017l\304L9x\030\017\205`\003\000\000\017\021B\020H\211UpH\211P\030H\201\373\377\003\000\000w\004H\211UhH\201\371\377\003\000\000v\bf\017\357\300\017\021B H\215\005\313\311\023\000H9\305\017\225\300\017\266\300H\301\340\002H\t\330H\203\310\001I\211E\bH\211\310H\203\310\001H\211B\bK\211L5\000\213\005y0\024\000I\215M\020\205\300\017\204_\371\377\3774\377H\211\317L\211\342\211\306\377\025\t\276\023\000H\211\301\351G\371\377\377f\017\037\204\000\000\000\000\000I\211\335I\301\355\tH\201\373\377)"..., "", "", "", "rProperty\000eader, could not find requested method: \"CanReadFile\"\nor the method was called with incorrect arguments.\narguments.\n\000\000\t", '\000' <repeats 15 times>, "\035\000\000\000UU\000\000\240\335\341YUU\000\000\t", '\000' <repeats 15 times>, "\020\232\002ZUU\000\000\r\000\000\000\000\000\000\000TimeStep"..., "", <error: Cannot access memory at address 0x10>, "", "", "", "", "", "", "", "", <error: Cannot access memory at address 0x6fd5a08a0f3b0400>, " x?\366\377\177\000\000\001\000\000\000\377\177", '\000' <repeats 18 times>, "\332\020\001", '\000' <repeats 13 times>, "з\371VUU", '\000' <repeats 11 times>, "tensions\000\000file_\020\270\371VUU\000\000\020\306\371VUU\000\000\300\263\371VUU\000\000`\017\372VUU\000\000is_direcq\000\000\000\000\000\000\000\200\270\371VUU\000\000\340\270\371VUU\000\000\000\271\371VUU\000\000\020\271\371VUU\000\000p\271\371VUU\000\000\220\271\371VUU\000\000\320\353\372VUU\000\000\020\354\372VUU\000\000\020\354\372VUU\000\000"..., "\204\300t\nL\213l$0\351w\377\377\377H\213|$\030\350=\271\375\3771\300\353\240H\307\300\377\377\377\377\353\303H\213D", "p\300\003ZUU\000\000\024\000\000\000\000\000\000\000\024\000\000\000\000\000\000\000ation\000\000\000\004\000\000\000\000\000\000\000\000\004;\017\212\240\325o\200h\000ZUU\000\000\200h\000ZUU\000\000\200L\254\365\377\177\000\000\220\267\371VUU\000\000\300\365\333YUU\000\000--Type <RET> for more, q to quit, c to continue without paging--
```
Full output: [backtrace.log](/uploads/81b008ea3d868fdb846e83ca81fef91b/backtrace.log)
This issue was originally reported at https://gitlab.archlinux.org/archlinux/packaging/packages/paraview/-/issues/3Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/22435Release ParaView 5.12.0-RC22024-01-11T10:51:01-05:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.12.0-RC2# Update ParaView
- Update the local copy of `release`.
- update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to ...# Update ParaView
- Update the local copy of `release`.
- update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `release` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Integrate changes.
- Make a commit for each of these `release` changes on a single topic
(suggested branch name: `update-to-v5.12.0`):
- [ ] Assemble release notes into `Documentation/release/ParaView-5.12.0.md`.
- [ ] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.12.0-RC2 44aa28bd3151d850dea75a937d50e3141493bdaf
echo 5.12.0-RC2 > version.txt
git commit -m 'Update version number to 5.12.0-RC2' version.txt
```
- Make a commit for each of these `release`-only changes
- [ ] `.gitmodules` to track the `paraview/release` branch of VTK
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups
- Create a merge request targeting `release`
- [ ] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [ ] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [ ] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [ ] Pull the script for each release; it may have been updated since it
was last used
- [ ] Add your development fork as a remote named `gitlab`
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m 44aa28bd3151d850dea75a937d50e3141493bdaf`
- [ ] The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [ ] Run the test with `Do: test` and get a green dashboard.
- [ ] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.12.0-RC2' v5.12.0-RC2 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.12.0-RC2`)
- Upload tarballs to `paraview.org`
- [ ] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [ ] `rsync -rptv $tarballs web:ParaView_Release/v5.12/`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Update ParaView-Superbuild
- [ ] Update release branch for **paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [ ] Create new branch `git checkout -b update-to-v5.12.0-RC2 release`
- Integrate changes.
- Update versions
- [ ] Guide selections in `versions.cmake` and ensure that the paraview
http URL source is the _DEFAULT_ source.
- [ ] `paraview_SOURCE_SELECTION` version in `README.md`
- [ ] `PARAVIEW_VERSION_DEFAULT` in CMakeLists.txt
- [ ] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [ ] ARG PARAVIEW_TAG=v5.12.0-RC2
- [ ] ARG SUPERBUILD_TAG=v5.12.0-RC2
- [ ] ARG PARAVIEW_VERSION_STRING=paraview-5.12
- [ ] Commit changes
- [ ] `git add README.md versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [ ] `git commit -m "Update the default version to 5.12.0-RC2"`
- Make a commit for each of these `release`-only changes
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `release` is `master`)
- [ ] Create a commit which will be tagged:
- [ ] `git commit --allow-empty -m "paraview: add release 5.12.0"`
- [ ] Create tag: `git tag -a -m 'ParaView superbuild 5.12.0-RC2' v5.12.0-RC2 HEAD`
- [ ] Create a commit that changes the paraview _DEFAULT_ source to the git
url source in the `versions.cmake` file.
- [ ] Force `5.12.0-RC2` in CMakeLists.txt
- [ ] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.12.0-RC2" CACHE STRING "Force version to 5.12.0-RC2" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [ ] Create fixup commit with the above changes `git commit -a --fixup=@`. The fixup commit will prevent merging of the temporary code above; it will be removed in a future step.
- [ ] Create a merge request targeting `release`
- [ ] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [ ] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [ ] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [ ] Pull the script for each release; it may have been updated since it
was last used
- [ ] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m f1d34a7bd18b3e2b97d431890a2936a21153a156`
- [ ] Make sure that the backporting directive in the merge-request
description skips the last commit such as: `Backport: master:HEAD~`
- Build binaries
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [x] Remove fixup commit: `git reset --hard @^`
- [ ] Get positive review
- [ ] Force push `git push -f gitlab`
- [ ] `Do: merge`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
# Sign Windows binaries
- [x] Request Windows binary signings (only .exe archives) on the Package
Signing repo. Example request [here][win-sign-example].
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0-RC2.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0-RC2.app/`
# Validating binaries
For each binary, open the Python shell and run the following:
```python
import numpy
s = Show(Sphere())
ColorBy(s, ('POINTS', 'Normals', 'X'))
Show(Text(Text="$A^2$"))
```
Check that
- Getting started guide opens
- Help lists Readers, Writers, Filters, and Sources properly
- Examples load and match thumbnails in dialog
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs ("Enable Ray Tracing" property in View panel)
- OptiX pathtracing runs (not macOS)
- ref. !22372 for current expected results
- IndeX runs (load pvNVIDIAIndeX plugin, add a Wavelet dataset, change representaiton to NVIDIA IndeX)
Binary checklist
- [x] macOS arm64
- [x] macOS x86\_64
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.12/`)
- [x] Ask @cory.quammen to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website from within the directory corresponding to www.paraview.org/files/
```
buildListing.sh
updateMD5sum.sh v5.12
```
- [ ] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.12.0-RC2`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.12.0-RC2`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
<!--
If making a non-RC release:
# Update documentation
- [ ] Submit a Merge Request for release that updates the version to 5.12.0 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [ ] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [ ] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.12.0.
- [ ] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [ ] Go to readthedocs.org and activate
- [ ] Write and publish blog post with release notes.
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
-->
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [x] Request DoD vulnerability scan
- [x] Request an XRInterface plugin validation using [TESTING.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/TESTING.md) protocol from KEU
<!--
If making a non-RC release:
- [ ] Request from comm@kitware.com an update of version number in "Download Latest Release" text on www.paraview.org
- [ ] Move unclosed issues in GitLab to the next release milestone in GitLab
-->
/cc @ben.boeckel
/cc @cory.quammen
/cc @charles.gueunet
/cc @mwestphal
[win-sign-example]: https://kwgitlab.kitware.com/software-process/package-signing/-/issues/12Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2024-01-05https://gitlab.kitware.com/paraview/paraview/-/issues/22443Undefined symbol at runtime when compiling static python32024-01-11T09:46:05-05:00Loic TetrelUndefined symbol at runtime when compiling static python3HI,
I am having an error at runtime after compiling paraview with python:
```
./bin/paraview
./bin/paraview: symbol lookup error: [REDACTED]/paraview-test/build/bin/../lib/libvtkRenderingMatplotlib-pv5.11.so.1: undefined symbol: PyTupl...HI,
I am having an error at runtime after compiling paraview with python:
```
./bin/paraview
./bin/paraview: symbol lookup error: [REDACTED]/paraview-test/build/bin/../lib/libvtkRenderingMatplotlib-pv5.11.so.1: undefined symbol: PyTuple_Type
```
OS: ubuntu 20.04
On `master` at 53257ab20c6ec6bc42b7ad2dc9e4c28ec05a123a using:
```sh
cmake -DPARAVIEW_USE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB -DCMAKE_BUILD_TYPE=Release ..
```
By default CMake find my locally compiled python in `usr/local` (which is static by default following [python doc](https://docs.python.org/3/using/unix.html#building-python)).
Working with python dynamic lib in `/usr` (shipped with ubuntu in `/usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0`). Dynamic lib is automatically used by CMake in that case.
```sh
-DPython3_EXECUTABLE=/usr/bin/python3
```
additional files:
[pv-python-dynamic.log](/uploads/95b2b291f56d66c5d59143cb3d7be9f8/pv-python-dynamic.log)
[pv-python-static.log](/uploads/a14555b36e4cd2a25ac973d3950a09c2/pv-python-static.log)
Thanks,https://gitlab.kitware.com/paraview/paraview/-/issues/13249StreamTracer segfault on a dataset without 3D cell2024-01-11T08:14:39-05:00Kitware RobotStreamTracer segfault on a dataset without 3D cell**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13249). Further discussion may take place here.**
---
Given the attached csv file I get different segfaults. This is all with PV...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13249). Further discussion may take place here.**
---
Given the attached csv file I get different segfaults. This is all with PV 3.14.1, happens in official binaries, as well as in a custom-compiled RelWithDebInfo build. Ubuntu Lucid, x86_64.
1st situation:
- Open csv file, apply default reader settings, data in table looks good
- Add a Table to Points filter, X column=x, etc
- Interestingly, the data at this point consists of a single cell with 25000 points
- Add a calculator filter, name result array 'v', expression 'vx*iHat+vy*jHat+vz*kHat'
- Newly added vector data looks good in table view
- Add a Mask points filter to the calculator output, #points=200, random sampling
- Add Streamtracer with custom source, input=calculator, source=maskpoints, apply
- SEGFAULT
```
Partial stack trace:
#0 0x00007f0390642976 in _int_malloc (av=0x7f0390945e40, bytes=112) at malloc.c:4635
#1 0x00007f03906437de in *__GI___libc_malloc (bytes=112) at malloc.c:3660
#2 0x00007f0390c2c24d in operator new(unsigned long) () from /usr/lib/libstdc++.so.6
#3 0x00007f0391eba342 in vtkPoints::New (dataType=10) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkPoints.cxx:51
#4 0x00007f0392b8e830 in vtkCell (this=0x330cea0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCell.cxx:24
#5 0x00007f0392d7f94e in vtkVertex (this=0x0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkVertex.cxx:29
#6 0x00007f0392d7fa40 in vtkVertex::New () at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkVertex.cxx:25
#7 0x00007f0392d0c840 in vtkPolyVertex (this=0x3a6f1c0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPolyVertex.cxx:31
#8 0x00007f0392d0c910 in vtkPolyVertex::New () at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPolyVertex.cxx:26
#9 0x00007f0392be49fc in vtkGenericCell::SetCellType (this=0x3a7bde0, cellType=2) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkGenericCell.cxx:364
#10 0x00007f0392cf2a75 in vtkGenericCell::SetCellTypeToPolyVertex (this=0x3a0a260, cellId=<value optimized out>, cell=0x3a7bde0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkGenericCell.h:98
#11 vtkPolyData::GetCell (this=0x3a0a260, cellId=<value optimized out>, cell=0x3a7bde0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPolyData.cxx:396
#12 0x00007f0392b64942 in vtkAbstractInterpolatedVelocityField::FunctionValues (this=0x27daaa0, dataset=0x3a0a260, x=0x2526450, f=0x3a14010) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkAbstractInterpolatedVelocityField.cxx:134
#13 0x00007f0392c82715 in vtkInterpolatedVelocityField::FunctionValues (this=0x27daaa0, x=0x2526450, f=0x3a14010) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkInterpolatedVelocityField.cxx:79
#14 0x00007f0391ecb8f2 in vtkRungeKutta45::ComputeAStep (this=0x28b1380, xprev=0x7fff94dd5c60, dxprev=<value optimized out>, xnext=<value optimized out>, t=<value optimized out>, delT=@0x7fff94dd5cb0, error=<value optimized out>)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkRungeKutta45.cxx:268
#15 0x00007f0391ecbd3f in vtkRungeKutta45::ComputeNextStep (this=0x28b1380, xprev=0x7fff94dd5c60, dxprev=0x0, xnext=0x7fff94dd5c40, t=<value optimized out>, delT=@0x7fff94dd5cb0, delTActual=<value optimized out>, minStep=24, maxStep=0, maxError=39, estErr=@0x7fff94dd5cc8)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkRungeKutta45.cxx:127
#16 0x00007f0391ecc36c in vtkRungeKutta45::ComputeNextStep (this=0x0, xprev=0x4000122c, xnext=<value optimized out>, t=0, delT=<value optimized out>, delTActual=<value optimized out>, minStep=0, maxStep=0, maxError=39, error=<value optimized out>)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkRungeKutta45.h:93
#17 0x00007f03944ef742 in vtkStreamTracer::Integrate (this=0x3aef950, input0=<value optimized out>, output=<value optimized out>, seedSource=0x29e8a60, seedIds=<value optimized out>, integrationDirections=<value optimized out>, lastPoint=0x7fff94dd5d80, func=0x27daaa0,
maxCellSize=25000, vecName=0x1da3680 "v", inPropagation=@0x7fff94dd5da8, inNumSteps=@0x7fff94dd5da0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:827
#18 0x00007f03944f106c in vtkStreamTracer::RequestData (this=0x3aef950, inputVector=<value optimized out>, outputVector=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:468
#19 0x00007f03974b62e5 in vtkPStreamTracer::RequestData (this=0x3aef950, request=0x347f9d0, inputVector=0x3b0d920, outputVector=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Parallel/vtkPStreamTracer.cxx:334
#20 0x00007f0392bd7da4 in vtkExecutive::CallAlgorithm (this=0x3af0700, request=0x347f9d0, direction=<value optimized out>, inInfo=0x3b0d920, outInfo=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkExecutive.cxx:747
#21 0x00007f0392bcb71c in vtkDemandDrivenPipeline::ExecuteData (this=0x3af0700, request=0x347f9d0, inInfo=0x3b0d920, outInfo=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:507
#22 0x00007f0392bac711 in vtkCompositeDataPipeline::ExecuteData (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:391
#23 0x00007f0392bce7cb in vtkDemandDrivenPipeline::ProcessRequest (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:279
#24 0x00007f0392d580f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#25 0x00007f0392ba95d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#26 0x00007f0392baa886 in vtkCompositeDataPipeline::ForwardUpstream (this=0x2a554c0, request=0x347f9d0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:215
#27 0x00007f0392bce775 in vtkDemandDrivenPipeline::ProcessRequest (this=0x2a554c0, request=0x347f9d0, inInfoVec=0x1d75470, outInfoVec=0x3a8f300) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:265
#28 0x00007f0392d580f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x2a554c0, request=0x347f9d0, inInfoVec=0x1d75470, outInfoVec=0x3a8f300) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#29 0x00007f0392ba95d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x2a554c0, request=0x347f9d0, inInfoVec=0x1d75470, outInfoVec=0x3a8f300) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#30 0x00007f0392bce50f in vtkDemandDrivenPipeline::UpdateData (this=0x2a554c0, outputPort=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:449
#31 0x00007f0392d5713b in vtkStreamingDemandDrivenPipeline::Update (this=0x2a554c0, port=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:326
#32 0x00007f03a3364d73 in vtkSISourceProxyCommand (arlu=0x16ac8d0, ob=0x3af78a0, method=<value optimized out>, msg=..., resultStream=...) at /home/paulmlocal/c/paraview-3.14.1-reldebinfo/ParaViewCore/ServerImplementation/vtkSISourceProxyClientServer.cxx:114
#33 0x00007f039936069f in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x16ac8d0, css=..., midx=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:379
#34 0x00007f039935f53e in vtkClientServerInterpreter::ProcessOneMessage (this=0x16ac8d0, css=..., message=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:214
#35 0x00007f039935f68d in vtkClientServerInterpreter::ProcessStream (this=0x16ac8d0, css=...) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:183
```
2nd situation (similar, but using Python calculator):
- Open csv file, apply default reader settings, data in table looks good
- Add a Table to Points filter, X column=x, etc
- Add a Python calculator filter, name result array 'v', expression 'hstack([vx,vy,vz])'
- Newly added vector data looks good in table view
- Add a Mask points filter to the calculator output, #points=200, random sampling
- Add Streamtracer with custom source, input=calculator, source=maskpoints, apply
- SEGFAULT
```
Partial stack trace:
#0 vtkPointLocator::FindClosestPoint (this=0x2aa6b20, x=0x7fffbda168b0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPointLocator.cxx:205
#1 0x00007fd0e433e9bc in vtkPointSet::FindCell (this=0x32f1350, x=0x7fffbda168b0, cell=0x0, gencell=0x40dde40, cellId=-1, tol2=<value optimized out>, subId=@0x7fffbda1665c, pcoords=0x2e57390, weights=0x2e5f020)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPointSet.cxx:291
#2 0x00007fd0e41b97f4 in vtkAbstractInterpolatedVelocityField::FunctionValues (this=0x2e57330, dataset=0x32f1350, x=0x7fffbda168b0, f=0x7fffbda168d0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkAbstractInterpolatedVelocityField.cxx:160
#3 0x00007fd0e42d7715 in vtkInterpolatedVelocityField::FunctionValues (this=0x2e57330, x=0x7fffbda168b0, f=0x7fffbda168d0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkInterpolatedVelocityField.cxx:79
#4 0x00007fd0e5b44323 in vtkStreamTracer::Integrate (this=0x2e2d3e0, input0=0x1, output=<value optimized out>, seedSource=0x40dbb80, seedIds=<value optimized out>, integrationDirections=<value optimized out>, lastPoint=0x7fffbda169d0, func=0x2e57330, maxCellSize=25000,
vecName=0x3eca270 "v", inPropagation=@0x7fffbda169f8, inNumSteps=@0x7fffbda169f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:696
#5 0x00007fd0e5b4606c in vtkStreamTracer::RequestData (this=0x2e2d3e0, inputVector=<value optimized out>, outputVector=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:468
#6 0x00007fd0e8b0b2e5 in vtkPStreamTracer::RequestData (this=0x2e2d3e0, request=0x40daaf0, inputVector=0x2e233b0, outputVector=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Parallel/vtkPStreamTracer.cxx:334
#7 0x00007fd0e422cda4 in vtkExecutive::CallAlgorithm (this=0x2e28a20, request=0x40daaf0, direction=<value optimized out>, inInfo=0x2e233b0, outInfo=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkExecutive.cxx:747
#8 0x00007fd0e422071c in vtkDemandDrivenPipeline::ExecuteData (this=0x2e28a20, request=0x40daaf0, inInfo=0x2e233b0, outInfo=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:507
#9 0x00007fd0e4201711 in vtkCompositeDataPipeline::ExecuteData (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:391
#10 0x00007fd0e42237cb in vtkDemandDrivenPipeline::ProcessRequest (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:279
#11 0x00007fd0e43ad0f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#12 0x00007fd0e41fe5d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#13 0x00007fd0e41ff886 in vtkCompositeDataPipeline::ForwardUpstream (this=0x2aa7360, request=0x40daaf0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:215
#14 0x00007fd0e4223775 in vtkDemandDrivenPipeline::ProcessRequest (this=0x2aa7360, request=0x40daaf0, inInfoVec=0x411f910, outInfoVec=0x40d6a70) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:265
#15 0x00007fd0e43ad0f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x2aa7360, request=0x40daaf0, inInfoVec=0x411f910, outInfoVec=0x40d6a70) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#16 0x00007fd0e41fe5d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x2aa7360, request=0x40daaf0, inInfoVec=0x411f910, outInfoVec=0x40d6a70) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#17 0x00007fd0e422350f in vtkDemandDrivenPipeline::UpdateData (this=0x2aa7360, outputPort=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:449
#18 0x00007fd0e43ac13b in vtkStreamingDemandDrivenPipeline::Update (this=0x2aa7360, port=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:326
#19 0x00007fd0f49b9d73 in vtkSISourceProxyCommand (arlu=0x2370780, ob=0x2e2ccf0, method=<value optimized out>, msg=..., resultStream=...) at /home/paulmlocal/c/paraview-3.14.1-reldebinfo/ParaViewCore/ServerImplementation/vtkSISourceProxyClientServer.cxx:114
#20 0x00007fd0ea9b569f in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x2370780, css=..., midx=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:379
#21 0x00007fd0ea9b453e in vtkClientServerInterpreter::ProcessOneMessage (this=0x2370780, css=..., message=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:214
#22 0x00007fd0ea9b468d in vtkClientServerInterpreter::ProcessStream (this=0x2370780, css=...) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:183
#23 0x00007fd0f43d970c in vtkPVSessionCore::ExecuteStreamInternal (this=0x236aca0, stream=..., ignore_errors=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerImplementation/vtkPVSessionCore.cxx:636
#24 0x00007fd0f43d7368 in vtkPVSessionCore::ExecuteStream (this=0x236aca0, location=1, stream=..., ignore_errors=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerImplementation/vtkPVSessionCore.cxx:606
#25 0x00007fd0f43d49f2 in vtkPVSessionBase::ExecuteStream (this=0x236e920, location=1, stream=..., ignore_errors=false) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerImplementation/vtkPVSessionBase.cxx:173
#26 0x00007fd0f4cfde65 in vtkSMProxy::ExecuteStream (this=<value optimized out>, stream=..., ignore_errors=false, location=1) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerManager/vtkSMProxy.cxx:2091
#27 0x00007fd0f4ce9110 in vtkSMOutputPort::UpdatePipelineInternal (this=0x303b7b0, time=<value optimized out>, doTime=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerManager/vtkSMOutputPort.cxx:211
#28 0x00007fd0f4d49d10 in vtkSMSourceProxy::UpdatePipeline (this=0x303c760, time=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerManage
```https://gitlab.kitware.com/paraview/paraview/-/issues/21351ParaView-based application unexpectedly use vtk system2024-01-11T04:15:48-05:00Nicolas VuailleParaView-based application unexpectedly use vtk systemWhile running a ParaView-based application on a system where another VTK is in the path (typically installed system-wide), using PythonCalculator crashes the application.
* SimpleParaView example (Examples/CustomApplications/SimpleParaV...While running a ParaView-based application on a system where another VTK is in the path (typically installed system-wide), using PythonCalculator crashes the application.
* SimpleParaView example (Examples/CustomApplications/SimpleParaView)
* edit `client/ParaViewFilters.xml` to add
```
<Proxy group="filters" name="PythonCalculator" icon=":/pqWidgets/Icons/pqClip.svg"/>
```
* build against ParaView master
* launch `./simple_paraview -v TRACE`
* load a data (tested with disk_out_ref)
* PythonCalculator
* Expression = 42
* Apply
* crash
Uninstalling the VTK-system solves the issue.
log ends with
```
( 21.473s) [paraview ] pqPropertiesPanel.cxx:138 9| . applying changes to `PythonCalculator1`
( 21.474s) [paraview ] vtkSISourceProxy.cxx:228 9| . { PythonCalculator1: update pipeline(0, 0.000000, true)
( 21.474s) [paraview ]vtkDemandDrivenPipeline:174 9| . . vtkPythonCalculator (0x55b847116fb0) execute-data-object
( 21.474s) [paraview ]vtkDemandDrivenPipeline:174 9| . . vtkPVPostFilter (0x55b8468a14c0) execute-data-object
( 21.474s) [paraview ]vtkDemandDrivenPipeline:222 9| . . vtkPythonCalculator (0x55b847116fb0) execute-information
( 21.474s) [paraview ]vtkDemandDrivenPipeline:222 9| . . vtkPVPostFilter (0x55b8468a14c0) execute-information
( 21.474s) [paraview ]vtkStreamingDemandDrive:164 9| . . vtkPVPostFilter (0x55b8468a14c0) execute-update-time
( 21.474s) [paraview ]vtkStreamingDemandDrive:164 9| . . vtkPythonCalculator (0x55b847116fb0) execute-update-time
( 21.474s) [paraview ]vtkStreamingDemandDrive:206 9| . . vtkPythonCalculator (0x55b847116fb0) execute-time-dependent-information
( 21.474s) [paraview ]vtkStreamingDemandDrive:206 9| . . vtkPVPostFilter (0x55b8468a14c0) execute-time-dependent-information
( 21.474s) [paraview ]vtkStreamingDemandDrive:318 9| . . vtkPVPostFilter (0x55b8468a14c0) execute-update-extent
( 21.474s) [paraview ]vtkStreamingDemandDrive:318 9| . . vtkPythonCalculator (0x55b847116fb0) execute-update-extent
( 21.474s) [paraview ]vtkDemandDrivenPipeline:259 9| . . vtkPythonCalculator (0x55b847116fb0) execute-data
( 21.474s) [paraview ] vtkSISourceProxy.cxx:305 9| . . { PythonCalculator1: execute
( 21.475s) [paraview ]vtkPythonInterpreter.cx:785 9| . . . calling Py_SetProgramName(/usr/lib/vtkpython) to aid in setup of Python prefix.
( 21.484s) [paraview ]vtkPythonInterpreter.cx:150 9| . . . adding module search path /home/nicolas/ParaView/master/build/lib/python3.10/site-packages
( 21.484s) [paraview ]vtkPythonInterpreter.cx:150 9| . . . adding module search path //lib/python3.10/site-packages
Loguru caught a signal: SIGSEGV
Stack trace:
1 0x7f71daab8660 /usr/lib/libvtkCommonCore.so.1(+0xab6660) [0x7f71daab8660]
0 0x7f72021ac560 /usr/lib/libc.so.6(+0x42560) [0x7f72021ac560]
( 21.494s) [paraview ] :0 FATL| Signal: SIGSEGV
```Nicolas VuailleNicolas Vuaillehttps://gitlab.kitware.com/paraview/paraview/-/issues/22438XRInterface plugin: Native interactions (scale, move, rotate) are not working...2024-01-09T13:23:28-05:00Mathieu Westphal (Kitware)XRInterface plugin: Native interactions (scale, move, rotate) are not working reliably with OpenVRNative grip interactions (https://www.kitware.com/navigation-basics-in-virtual-reality-with-paraview/) are not working reliably.
Sometimes they do, sometimes they dont.
Steps to reproduce:
- run ParaView, load XRInterface plugin
- Wav...Native grip interactions (https://www.kitware.com/navigation-basics-in-virtual-reality-with-paraview/) are not working reliably.
Sometimes they do, sometimes they dont.
Steps to reproduce:
- run ParaView, load XRInterface plugin
- Wavelet, Apply
- OpenVR, SendToXR
- Press A on both controllers and move hands (Valve Index Grip interactions)
- Not working
- If working, repeat until it does not work
- In my tests, it worked 3/10 times roughly
Notes:
- Works perfectly with OpenXR
- **This is a reggresion!** broken between def2b450a8 and 19627031fehttps://gitlab.kitware.com/paraview/paraview/-/issues/22440Record Test, Error message when cicking on plugin toolbar button2024-01-09T11:28:41-05:00Loïc GaillardRecord Test, Error message when cicking on plugin toolbar buttonWhen using the `Record Test` feature from paraview, if you click on a toolbar button from a loaded plugin, it will log an error message in the console : `
critical: Unable to to determine name for Object QAction(0x1fbf473f0b0) because ...When using the `Record Test` feature from paraview, if you click on a toolbar button from a loaded plugin, it will log an error message in the console : `
critical: Unable to to determine name for Object QAction(0x1fbf473f0b0) because a parent GUIMyToolBarPlugin(0x7ffeb04b2a80) is not a top-level widget. Name so far = "GUIMyToolBarPlugin0/MyToolBarActions/MyToolBarActions0/QAction0"`
Steps to reproduce :
- Choose a plugin from the paraview example folder, i tried with `GUIMyToolBar` & `SourceToolbar` (both logs the error).
- Load the plugin.
- Start recording a test
- Click on the plugin toolbar button
The issue seems related to QTesting.Loïc GaillardLoïc Gaillardhttps://gitlab.kitware.com/paraview/paraview/-/issues/22411Windows v5.12.0-RC1 Windows/Save Animation/.avi fails2024-01-08T13:43:58-05:00Phil SmithWindows v5.12.0-RC1 Windows/Save Animation/.avi failsWhen saving .avi animation with with Windows 11 using v5.12.0-RC1, here is the error that is produced:
```
Warning: In vtkSMSaveAnimationProxy.cxx, line 398
vtkSMSaveAnimationProxy (000001F3CAF0B920): The requested resolution...When saving .avi animation with with Windows 11 using v5.12.0-RC1, here is the error that is produced:
```
Warning: In vtkSMSaveAnimationProxy.cxx, line 398
vtkSMSaveAnimationProxy (000001F3CAF0B920): The requested resolution '(874, 500)' has been changed to '(872, 500)' to match format specification.
Generic Warning: In vtkSMPropertyHelper.cxx, line 570
Failed to locate property: FileName
Generic Warning: In vtkSMPropertyHelper.cxx, line 367
Call not supported for the current property type.
ERROR: In vtkAVIWriter.cxx, line 77
vtkAVIWriter (000001F3C99B4D50): Write:Please specify a FileName
```
Here are the steps to reproduce:
1. Open Can, Apply
2. Save Animation
3. Select the directory you would like to save it to, enter a file name to save it to as well, select OK
4. Use the default selections on the following screen and select OK
5. It appears to save it, however, the above error is displayed, and no file is saved.https://gitlab.kitware.com/paraview/paraview/-/issues/223945.12.0-RC1 crashes on Windows saving animation mp42024-01-08T13:42:26-05:00W. Alan Scott5.12.0-RC1 crashes on Windows saving animation mp4We have a crash trying to save an mp4 animation. Here is how to replicate:
* 5.12.0-RC1, Windows, builtin server.
* can.exo. Apply.
* File/ Save Animation. mp4. OK, OK
This will crash.
First reported here: https://discourse.paravi...We have a crash trying to save an mp4 animation. Here is how to replicate:
* 5.12.0-RC1, Windows, builtin server.
* can.exo. Apply.
* File/ Save Animation. mp4. OK, OK
This will crash.
First reported here: https://discourse.paraview.org/t/paraview-5-12-0-rc1-crashes-when-exporting-animation-in-windows-11/133675.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21772ParaView help menu item Reader, Filter, and Writer Reference Search tab not a...2024-01-08T11:23:19-05:00Phil SmithParaView help menu item Reader, Filter, and Writer Reference Search tab not able to search@spiros.tsalikis @wascott
This was tested with Windows ParaView 5.11.0 Master. To Reproduce
- Select Help Menu
- Select Reader,Filter, and Writer Reference
- Select Search tab
- Enter what you would like to search for and Click on sea...@spiros.tsalikis @wascott
This was tested with Windows ParaView 5.11.0 Master. To Reproduce
- Select Help Menu
- Select Reader,Filter, and Writer Reference
- Select Search tab
- Enter what you would like to search for and Click on search
It always says Your search did not match any documents.
This is even when what you search for is in the present window.5.12 (Winter 2023)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22392Updated Fast color map2024-01-08T11:16:38-05:00W. Alan ScottUpdated Fast color mapAfter further evaluation, we (Ken, Francesca and I) determined that we needed a few more control points to create a really good color map. Thus, we need to update the Fast map. It will now include 9 control points. Here is the new Fast...After further evaluation, we (Ken, Francesca and I) determined that we needed a few more control points to create a really good color map. Thus, we need to update the Fast map. It will now include 9 control points. Here is the new Fast map, along with the old Fast map.
![Old_and_new_Fast2](/uploads/fe6213992f05eb3808a9bf8ac6fa32a2/Old_and_new_Fast2.png)
This must be done for 5.12.0-RC2.
Attached is the .xml from Francesca Samsel. I am also including the text version. Please use these control points for the Fast map.
[Fast-30FINAL.xml](/uploads/8ad43bc7c2782d500806b7fada0d8e25/Fast-30FINAL.xml)
```
<ColorMaps>
<ColorMap name="Divergent 1" space="RGB" interpolationspace="lab" interpolationtype="linear" creator="CCC-Tool">
<Point x="0" o="1" r="0.05639999999999999" g="0.05639999999999999" b="0.47" cms="1" isMoT="true"/>
<Point x="0.17159223942480895" o="1" r="0.24300000000000013" g="0.4603500000000004" b="0.81" cms="1" isMoT="true"/>
<Point x="0.2984914818394138" o="1" r="0.3568143826543521" g="0.7450246485363142" b="0.954367702893722" cms="1" isMoT="true"/>
<Point x="0.4321287371255907" o="1" r="0.6882" g="0.93" b="0.9179099999999999" cms="1" isMoT="true"/>
<Point x="0.5" o="1" r="0.8994959551205902" g="0.944646394975174" b="0.7686567142818399" cms="1" isMoT="true"/>
<Point x="0.5882260353170073" o="1" r="0.957107977357604" g="0.8338185108985666" b="0.5089156299842102" cms="1" isMoT="true"/>
<Point x="0.7061412605695164" o="1" r="0.9275207599610714" g="0.6214389091739178" b="0.31535705838676426" cms="1" isMoT="true"/>
<Point x="0.8476395308725272" o="1" r="0.8" g="0.3520000000000001" b="0.15999999999999998" cms="1" isMoT="true"/>
<Point x="1" o="1" r="0.59" g="0.07670000000000013" b="0.11947499999999994" cms="1" isMoT="true"/>
<NaN r="0" g="0" b="0"/>
<Above r="0" g="0" b="0"/>
<Below r="0" g="0" b="0"/>
</ColorMap>
</ColorMaps>
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21723Increasing memory usage when reading temporal data2024-01-08T05:29:49-05:00Thomas GallandIncreasing memory usage when reading temporal dataParaView memory consumption seems increasing when reading temporal data.
The following chart shows the consumption of the physical memory (RSS) with the `Xdmf` reader on a ≃ 20GB dataset. \
Each red line correspond to a new timestep req...ParaView memory consumption seems increasing when reading temporal data.
The following chart shows the consumption of the physical memory (RSS) with the `Xdmf` reader on a ≃ 20GB dataset. \
Each red line correspond to a new timestep request:
![image](/uploads/f128826c5190c44ae1f00c79e95505f8/image.png)
Same trends are observed with other readers. For example when opening `.vtm` files :
![image](/uploads/edef16aad68220150060ed3a1b479a33/image.png)
Several things to note at this point :
- In each case, things seems to stabilize over time.
- Going back to a previously read timestep or reading a new one has no significative impact on the results.
- Changing the way to display the output from `Render View` to `SpreadSheet View` as no significative impact as well.
- Using pvpython scripting **without rendering involved** shows the same results.
One of the possible track to follow was to ensure that the animation cache was used correctly. \
When opening a smaller dataset (`Xdmf` ≃ 3GB) and setting the animation cache on and off, we observe the following results:
![image](/uploads/51e4ca4516e650dcb2305efa545bc479/image.png)
![image](/uploads/10867d56326ec5168dcb6a0dd8233ada/image.png)
We can see that:
- With the animation cache, the memory consumption increases on each timestep. Then by looping the animation, memory consumption doesn't change anymore.
- Without the animation cache, I have the same memory consumption, without the plateau once looping.
The first situation seems coherent, as caching data increases naturally the memory usage; then no more cost when eveything is cached. \
But without cache, we can expect no increase of the memory consumption between each timestep. It looks like the data is cached anyway, but not used during the loop.
When trying to reproduce it with VTK alone (with the same input data, `Xdmf` ≃ 3GB) we can observe similar trend as well :
![image](/uploads/f350f5b1a228d62ef19a94c072da75dc/image.png)
This may invalidate the fact that the animation cache is the problem.
Now when using no rendering pipeline at all :
![image](/uploads/7ad8ab61dc1eb73155abc59536b44135/image.png)
Among all the measures I made, this is the only case where memory consumption seems not growing.Thomas GallandThomas Gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/22439Duplicate context-menu action in the edit menu of ParaView2024-01-08T04:50:35-05:00Mathieu Westphal (Kitware)Duplicate context-menu action in the edit menu of ParaViewThere are a few context menu actions that are not available in any actual menu of ParaView.
They should be added to the edit menu.
pipeline browser:
- Reload
- Change fileThere are a few context menu actions that are not available in any actual menu of ParaView.
They should be added to the edit menu.
pipeline browser:
- Reload
- Change filehttps://gitlab.kitware.com/paraview/paraview/-/issues/22108Paraview opens ADIOS2-VTX BP5 files as BP42024-01-05T11:38:23-05:00Massimiliano LeoniParaview opens ADIOS2-VTX BP5 files as BP4[I am filing with Paraview but this might as well be a VTK problem].
With the release of ADIOS2 2.9.0, BP5 is now the default file engine [cfr. https://github.com/ornladios/ADIOS2/releases/tag/v2.9.0 ]. I tried to open BP5-VTX files cre...[I am filing with Paraview but this might as well be a VTK problem].
With the release of ADIOS2 2.9.0, BP5 is now the default file engine [cfr. https://github.com/ornladios/ADIOS2/releases/tag/v2.9.0 ]. I tried to open BP5-VTX files created through my code that uses the newest version of ADIOS2 and I get a `BP4Reader` error, whereas running with a debugger I verified that the file is created by a `BP5Writer`.
I suspect Paraview should instead be using a `BP5Reader`.Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/17564core dump saving quadratic tetrahedra in Xdmf format2024-01-05T05:00:38-05:00Jean M. Favrecore dump saving quadratic tetrahedra in Xdmf formatGet a source 'Unstructured Cell Types' (version 5.4)
select "quadratic tet"
Save data.
you're greeded with the following message:
I do not know how to make that xdmf cell type
Invalid topology type id found in connectivity when pars...Get a source 'Unstructured Cell Types' (version 5.4)
select "quadratic tet"
Save data.
you're greeded with the following message:
I do not know how to make that xdmf cell type
Invalid topology type id found in connectivity when parsing mixed topology.
Qt has caught an exception thrown from an event handler.
Aborted (core dumped)5.12 (Winter 2023)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22393The IOSS reader is failing reading variables2024-01-04T21:24:45-05:00W. Alan ScottThe IOSS reader is failing reading variablesThe IOSS reader is failing reading variable data for a dataset. This shows with one file of the 640 file dataset. I am giving this file to @cory.quammen. It is ok to pass to anyone at Kitware, but file is DoNotRelease.
* 5 12.0-RC1, L...The IOSS reader is failing reading variable data for a dataset. This shows with one file of the 640 file dataset. I am giving this file to @cory.quammen. It is ok to pass to anyone at Kitware, but file is DoNotRelease.
* 5 12.0-RC1, Linux, builtin server.
* Open IOSS-VariablesDontRead-DoNotRelease.exo. Apply. This will read all blocks and variables.
* Try to paint by a variable from the Properties tab variable list. You can't. This is a bug.
* Delete the file.
* Tools/ Manage Plugins/ load the LegacyExodusReader.
* Open IOSS-VariablesDontRead-DoNotRelease.exo. Use the LegacyExodusReader. Turn on the variables. Apply.
* You will be able to paint by different variables from the Properties tab.
@spiros.tsalikis5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22436Aggregate Dataset Filter crashes in Catalyst2024-01-04T19:35:22-05:00W. Alan ScottAggregate Dataset Filter crashes in CatalystThe Aggregate dataset filter (I incorrectly reported as Redistribute Data Set Filter) is crashing in Catalyst API 1. Here is how to replicate.
* Run ParaView 5.11.0, remote server (16 ranks), Linux.
* Open g1s1. Apply.
* Merge Blocks. ...The Aggregate dataset filter (I incorrectly reported as Redistribute Data Set Filter) is crashing in Catalyst API 1. Here is how to replicate.
* Run ParaView 5.11.0, remote server (16 ranks), Linux.
* Open g1s1. Apply.
* Merge Blocks. (Aggregate dataset filter does not take multiblock data.)
* Aggregate dataset Filter. Number of target processes: 4. Apply.
* Extracts/ png.
* File/ Save State. Save as junkState.py file.
* pvbatch - I believe 16 ranks. junkState.py file.
* There will be a movie output of .png images.
* Going back to ParaView,
* File/ Save Catalyst State File
* Use this as the controlling script for a Catalyst run. This is primarily on Sparc, but has also been seen on Sierra.
* This will crash with an MPI error.
Note we don't think this is an MPI version issue, as other MPI areas of Catalyst work correctly.
I can't find a trace from Jeff, ask if needed.
As LANL has not seen this issue, this may need to be debugged at Sandia.
Contact is Jeff Mauldin.5.12.1 (Spring 2024)