# About Microsoft C++ exception: std::out\_of\_range
**URL:** https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494
**Category:** ParaView Support
**Created:** [October 12, 2022, 7:05pm UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494 "2022-10-12T19:05:32Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Cam](https://discourse.paraview.org/u/Cam)
#### Post date: [October 12, 2022, 7:05pm UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494/1 "2022-10-12T19:05:32Z")
I built ParaView on Windows using MSVC and Ninja. When I ran it in debug mode, I noticed there are a lot of exceptions. If I have objects in the scene and rotate my camera, I will get a lot of
`Exception thrown at 0x00007FFE2F184FD9 in paraview.exe: Microsoft C++ exception: std::out_of_range at memory location 0x000000283C0F4BB0.`
And occasionally get
`Exception thrown at 0x00007FFE2F184FD9 in paraview.exe: Microsoft C++ exception: bool at memory location 0x000000283C0F680B.`
Are these exceptions safe to ignore? Why can’t we fix them?
Thanks,
Cam
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 13, 2022, 2:45am UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494/2 "2022-10-13T02:45:35Z")
> [@Cam](#):
>
> Are these exceptions safe to ignore? Why can’t we fix them?
Definitely unexpected. I have a MSVC + Ninja build here and there is no exception at all. Open an issue ?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 13, 2022, 11:22am UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494/3 "2022-10-13T11:22:18Z")
Please clarity if your debugger is catching exceptions or if they are causing the ParaView to crash.
Also make sure your environment has the right Qt in your PATH.
---
### Author:  [@Cam](https://discourse.paraview.org/u/Cam)
#### Post date: [October 13, 2022, 4:28pm UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494/4 "2022-10-13T16:28:51Z")
Hi Cory,
It was the Microsoft debugger catching those exceptions. These exceptions are not fatal as the the application doesn’t crash.
---
### Author:  [@Cam](https://discourse.paraview.org/u/Cam)
#### Post date: [October 13, 2022, 6:09pm UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494/5 "2022-10-13T18:09:22Z")
Hi Cory and Mathieu,
I have attached a GIF in the original post.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 13, 2022, 11:37pm UTC](https://discourse.paraview.org/t/about-microsoft-c-exception-std-out-of-range/10494/6 "2022-10-13T23:37:17Z")
Looks like you are using Visual Studio Code. In the Debug controls under the Breakpoints section, you should be able to catch C++ exceptions when thrown. When you do that, you’ll see that an exception is thrown in `vtkPVDataDeliveryManagerInternals::GetDeliveredDataObject()`, but it is caught and handled properly. That might be what you are seeing.
As long as the exception is caught and handled, there is no problem to be fixed.