Fix occasional wmem_test failure, allocator destruction order matters

(should it?)

svn path=/trunk/; revision=49951

1 files changed, 1 insertions, 4 deletions

diff --git a/epan/wmem/wmem_test.c b/epan/wmem/wmem_test.c
index 6df0a65f1c..a9b59316c2 100644
--- a/epan/wmem/wmem_test.c
+++ b/epan/wmem/wmem_test.c
@@ -603,7 +603,7 @@ wmem_test_tree(void)
         wmem_tree_insert32(tree, i, GINT_TO_POINTER(i));
         g_assert(wmem_tree_lookup32(tree, i) == GINT_TO_POINTER(i));
     }
-    wmem_free_all(extra_allocator);
+    wmem_destroy_allocator(extra_allocator);
     for (i=0; i<CONTAINER_ITERS; i++) {
         g_assert(wmem_tree_lookup32(tree, i) == NULL);
         g_assert(wmem_tree_lookup32_le(tree, i) == NULL);
@@ -646,9 +646,6 @@ wmem_test_tree(void)
     }
     g_assert(seen_values == 10);
 
-    wmem_free_all(allocator);
-
-    wmem_destroy_allocator(extra_allocator);
     wmem_destroy_allocator(allocator);
 }