0004060: assertion failed [rem_idx != -1]: Unable to find existing allocation for shared memory segment to unmap (VMAllocationTracker.cpp - OpenFOAM Issue Tracking

ID	Project	Category	View Status	Date Submitted	Last Update

0004060	OpenFOAM	Bug	public	2024-02-29 21:41	2024-02-29 21:41

Reporter	mcrock	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	new	Resolution	open
Platform	GNU/Linux	OS	OpenSuSE	OS Version	12.3
Product Version	10

Summary	0004060: assertion failed [rem_idx != -1]: Unable to find existing allocation for shared memory segment to unmap (VMAllocationTracker.cpp
Description	My computer has recently updated to macOS Sonoma 14.3.1, and since then I have not been able to visualize my openFoam trials by using the command “paraFoam”. I began with using docker version 4.27.0 and thought that it might be an issue with that version, as per discussed here: Docker for Macos Sonoma 14.3.1 · Issue #7183 · docker/for-mac · GitHub 14 . In an attempt to resolve the issue, I reverted back to docker version 4.26.1. I am still having the same issue, which will be pasted below: 5edb65479128: gFHRcore_simplifiedMeshv4>> paraFoam Created temporary ‘gFHRcore_simplifiedMeshv4.OpenFOAM’ QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-openfoam’ assertion failed [rem_idx != -1]: Unable to find existing allocation for shared memory segment to unmap (VMAllocationTracker.cpp:745 remove_shared_mem) Trace/breakpoint trap I have not been able to find that many resources online to help with this issue and really need some guidance in solving it.
Steps To Reproduce	type "paraFoam" into any directory that has a mesh
Tags	No tags attached.

Date Modified	Username	Field	Change
2024-02-29 21:41	mcrock	New Issue