Dmitry Karpeyev committed 6723443

Fix to allow -options_monitor.
ThreadComm needs to be initialized before the options monitor is added,
as it opens a viewer, which uses PetscCommDuplicate(), which needs
ThreadComm keyval.\nMonitors need to be cancelled in PetscFinalize() to
release their viewer's memory before -malloc_dump reports it.

Comments (0)

Files changed (1)


   ierr = PetscGetHostName(hostname,256);CHKERRQ(ierr);
   ierr = PetscInfo1(0,"Running on machine: %s\n",hostname);CHKERRQ(ierr);
+  /* Ensure that threadcomm-related keyval exists, so that PetscOptionsSetFromOptions can use PetscCommDuplicate. */
+  ierr = PetscThreadCommInitializePackage();CHKERRQ(ierr);
   ierr = PetscOptionsCheckInitial_Components();CHKERRQ(ierr);
   /* Check the options database for options related to the options database itself */
   ierr = PetscOptionsSetFromOptions();CHKERRQ(ierr);
     ierr = PetscPythonInitialize(NULL,NULL);CHKERRQ(ierr);
-  ierr = PetscThreadCommInitializePackage();CHKERRQ(ierr);
       Setup building of stack frames for all function calls
   ierr = PetscInfo(NULL,"PetscFinalize() called\n");CHKERRQ(ierr);
+  /*
+    It should be safe to cancel the options monitors, since we don't expect to be setting options
+    here (at least that are worth monitoring).  Monitors ought to be released so that they release
+    whatever memory was allocated there before -malloc_dump reports unfreed memory.
+  */
+  ierr = PetscOptionsMonitorCancel();CHKERRQ(ierr);
   ierr = PetscFPTDestroy();CHKERRQ(ierr);