View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000050OpenFOAMBugpublic2010-10-01 12:452010-10-07 18:01
Reporteruser47Assigned Touser2 
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
PlatformSony VaioOSLinux MintOS VersionUbuntu 9.10
Summary0000050: Crash using DirectMappedVelocityFluxField
DescriptionDear developers and/or debuggers,

When using the directMappedVelocityFlux patch to remap the U field, pisoFoam crashes when using the NEARESTFACE option.

If interested, I can post the error message associated with the crash, but I've traced the origin back to the following piece of code in directMappedVelocityFluxFixedValueFvPatchField:

00209 newUValues = patch().patchSlice(newUValues);

The thing is that newUValues was declared slightly higher with

00176 vectorField newUValues;

but was not used/instantiated after that.
Reading the similar routine used in directMappedFixedValueFvPatchField.C, I guess the variable in brackets should be allUValues and not newUValues, leading to:

00209 newUValues = patch().patchSlice(allUValues);

This is however only an educated guess of yours truly..
Kind regards,

Francois.
Steps To ReproduceSee Description.
TagsModelling

Activities

user2

2010-10-01 13:16

  ~0000058

Thanks for the report - resolved under commit 5839fff42615cb23d1b8e7dc868e15b7147851fa

Issue History

Date Modified Username Field Change
2010-10-01 12:45 user47 New Issue
2010-10-01 12:57 user2 Assigned To => user2
2010-10-01 12:57 user2 Status new => assigned
2010-10-01 13:16 user2 Note Added: 0000058
2010-10-01 13:16 user2 Status assigned => resolved
2010-10-01 13:16 user2 Fixed in Version => 1.7.x
2010-10-01 13:16 user2 Resolution open => fixed
2010-10-07 18:01 user2 Tag Attached: Modelling