### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 25, 2023, 4:54pm UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/7 "2023-05-25T16:54:31Z")
Then you may want to keep going and inspect the content on `extensions_list` before the bad call on line 95 in pqFileDialogFilter.cxx
---
### Author:  [@guillaume\_Peillex](https://discourse.paraview.org/u/guillaume_Peillex)
#### Post date: [May 26, 2023, 11:18am UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/8 "2023-05-26T11:18:36Z")
I did it before opening this post and did not see anything particular. I remade it this morning and here is what i get:
```auto
QStringList (size = 88) = {[0] = "nc", [1] = "cdf", [2] = "elev", [3] = "ncd", [4] = "boundary", [5] = "hierarchy", [6] = "Flash", [7] = "flash", [8] = "xamr", [9] = "Xamr",
[10] = "XAMR", [11] = "inp", [12] = "aux", [13] = "inp", [14] = "bov", [15] = "g", [16] = "nc", [17] = "ncdf", [18] = "spcth-timeseries", [19] = "nc", [20] = "cdf", [21] = "elev",
[22] = "ncd", [23] = "nc", [24] = "cdf", [25] = "elev", [26] = "ncd", [27] = "ucd", [28] = "inp", [29] = "cgns", [30] = "hdf5", [31] = "h5", [32] = "gml", [33] = "xml", [34] = "claw",
[35] = "cmat", [36] = "cml", [37] = "h5", [38] = "ctrl", [39] = "curve", [40] = "ultra", [41] = "ult", [42] = "u", [43] = "ddcmd", [44] = "csv", [45] = "tsv", [46] = "txt", [47] = "CSV",
[48] = "TSV", [49] = "TXT", [50] = "dcm", [51] = "dcm", [52] = "dem", [53] = "dyn", [54] = "case", [55] = "CASE", [56] = "Case", [57] = "encas", [58] = "ENCAS", [59] = "Encas",
[60] = "sos", [61] = "SOS", [62] = "boundary", [63] = "hierarchy", [64] = "exvol", [65] = "facet", [66] = "Flash", [67] = "flash", [68] = "flash", [69] = "f5", [70] = "cas", [71] = "nc",
[72] = "cdf", [73] = "elev", [74] = "ncd", [75] = "nc", [76] = "cdf", [77] = "elev", [78] = "ncd", [79] = "nc", [80] = "cdf", [81] = "elev", [82] = "ncd", [83] = "nc", [84] = "cdf",
[85] = "elev", [86] = "ncd", [87] = "trg"}
```
In fact if the list is one element shorter, the crash does not occur. It definitely looks like memory related don’t you think?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 26, 2023, 11:20am UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/9 "2023-05-26T11:20:22Z")
I agree, however this memory is handled by Qt fully, I dont see how we could mess it up. Valgrind may be needed but I’d not get my hopes up 😕
---
### Author:  [@aron.helser](https://discourse.paraview.org/u/aron.helser)
#### Post date: [May 26, 2023, 1:32pm UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/10 "2023-05-26T13:32:39Z")
I would be suspicious of a library mis-match, potentially loading parts of Qt from an unexpected location. Try running paraview like `LD_DEBUG=libs paraview` and see if any of the loaded Qt libraries come from an unexpected system location.
---
### Author:  [@guillaume\_Peillex](https://discourse.paraview.org/u/guillaume_Peillex)
#### Post date: [May 26, 2023, 3:52pm UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/11 "2023-05-26T15:52:42Z")
I already tried valgrind but i’m facing a `valgrind unrecognised instruction at address` error.
---
### Author:  [@guillaume\_Peillex](https://discourse.paraview.org/u/guillaume_Peillex)
#### Post date: [May 26, 2023, 3:53pm UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/12 "2023-05-26T15:53:08Z")
Thanks for the hint Aron. I’ll give it a try.
---
### Author:  [@guillaume\_Peillex](https://discourse.paraview.org/u/guillaume_Peillex)
#### Post date: [June 7, 2023, 8:49am UTC](https://discourse.paraview.org/t/std-bad-alloc-when-clicking-on-open/12151/13 "2023-06-07T08:49:49Z")
I did not found the origin of the problem.
However i found a workaround by installing a proper gcc (8.5.0 or 8.3.0) with spack and the problem seems to be solved.
Thanks for your help.