# Paraview 5.10.1 automatically crashes with MFIX built-in case

**URL:** https://discourse.paraview.org/t/paraview-5-10-1-automatically-crashes-with-mfix-built-in-case/17645
**Category:** ParaView Support
**Created:** [July 2, 2026, 8:46am UTC](https://discourse.paraview.org/t/paraview-5-10-1-automatically-crashes-with-mfix-built-in-case/17645 "2026-07-02T08:46:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ultrayi](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/u/dec6dc/32.png) [@ultrayi](https://discourse.paraview.org/u/ultrayi)
#### Post date: [July 2, 2026, 8:46am UTC](https://discourse.paraview.org/t/paraview-5-10-1-automatically-crashes-with-mfix-built-in-case/17645/1 "2026-07-02T08:46:32Z")

</div>

ParaView keeps crashing whenever I try to “apply” after open the RES output files generated by the built-in Fluid Bed 2D case in MFIX.

OS： Win 10/ Win 11

Thanks a lot.

[FLUID\_BED\_TFM\_2D.RES](https://discourse.paraview.org/uploads/short-url/s7wyqj7fDI9eXsG13V58pM4N1SG.RES) (2.1 MB)

RES file name: FLUID\_BED\_TFM\_2D.RES ( not the one that include retarted data)

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 2, 2026, 1:55pm UTC](https://discourse.paraview.org/t/paraview-5-10-1-automatically-crashes-with-mfix-built-in-case/17645/2 "2026-07-02T13:55:53Z")

</div>

Confirmed crash on ParaView 6.1.1 on macOS.

Stack trace

```auto
Thread 0 Crashed:: paraview Dispatch queue: com.apple.main-thread
0 libvtkIOGeometry-pv6.1.6.1.dylib 0x125ced08c vtkMFIXReader::GetAllTimes(vtkInformationVector*) + 640
1 libvtkIOGeometry-pv6.1.6.1.dylib 0x125ce0474 vtkMFIXReader::RequestInformation(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 812
2 libvtkCommonExecutionModel-pv6.1.6.1.dylib 0x1064b9308 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 84
3 libvtkCommonExecutionModel-pv6.1.6.1.dylib 0x106525c60 vtkStreamingDemandDrivenPipeline::ExecuteInformation(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 56
4 libvtkCommonExecutionModel-pv6.1.6.1.dylib 0x1064af6c0 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 640
5 libvtkCommonExecutionModel-pv6.1.6.1.dylib 0x106524ccc vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 908
6 libvtkRemotingServerManager-pv6.1.6.1.dylib 0x1042a0e88 vtkSISourceProxy::UpdatePipelineInformation() + 188
7 libvtkRemotingApplication-pv6.1.6.1.dylib 0x110244c24 vtkSISourceProxyCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1568
8 libvtkRemotingClientServerStream-pv6.1.6.1.dylib 0x10323c768 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 260
9 libvtkRemotingClientServerStream-pv6.1.6.1.dylib

```

Would you mind creating an issue for this over at [gitlab.kitware.com/paraview/paraview](http://gitlab.kitware.com/paraview/paraview)? Thanks.
