avoid register/deregister of tmp fields

By default IOobject uses (REGISTER). When a tmp field is created, its name will be registered in the corresponding objectRegistry (invoking an allocation to add to the HashTable, plus calculation of a hash value etc). If the tmp leaves scope immediately, it is removed from the registry which incurs another delete in addition to that of the tmp itself.

marked this issue as related to #2758 (closed)

mentioned in commit 1685e8e4

mentioned in commit dfa5c05a

mentioned in commit da53fa74

mentioned in commit 5973afc3

mentioned in commit 45b07ecd

mentioned in commit 7bc4cda5

mentioned in commit 017bebbd

mentioned in commit 4c641615

mentioned in commit ae985e54

mentioned in commit d693d3dd

mentioned in commit 9a7dca8c

mentioned in commit 7016f50c

mentioned in commit 9b03a069

mentioned in commit f2789df4

mentioned in merge request !665 (merged)

There is a problem with order of cleanup at end:

log.chtMultiRegionFoam

This comes from the deletion of mappedPatchBase which stores some dimensionedUniformFields (just to use the eventNo checking in regIOobject).

Just run e.g. the tutorials/heatTransfer/chtMultiRegionFoam/multiRegionHeater under valgrind.

mentioned in commit d9c5a5d1

mentioned in commit 1ebb116d

mentioned in commit 2a3de550

mentioned in commit 75765764

mentioned in commit e16c133d

mentioned in commit 34c1dc6c

mentioned in commit b5bc8c07

mentioned in commit 52e5871d

mentioned in commit 052b78e8

mentioned in commit aedfb0b8

mentioned in commit fff30105

mentioned in commit fefe2b31

mentioned in commit d7cb3ee3

mentioned in commit 092db087

mentioned in commit 21196d8c

mentioned in commit 71d4a23e

mentioned in commit 33f20edb

mentioned in commit d9483f50

mentioned in commit 7bf0aaf9

mentioned in commit 710eb5c1

mentioned in commit 995a9705

mentioned in commit 51f150d8

mentioned in commit ec2b1be8

mentioned in commit c138f89c

mentioned in commit 8b73d068

closed