1009491 - Leaks when running xpcshell/toolkit/components/filewatcher/ xpcshell tests

Status: RESOLVED FIXED

(Testing :: XPCShell Harness, defect)

Description

[Alessio Placitelli [:Dexter]]

Attachment: simple_test.js

When executing the attached simple xpcshell test using the ./mach xpcshell-test simple_test.js command, the console prints a number of warnings:

From _tests: Kept 17699 existing; Added/updated 5; Removed 0 files and 0 directories.
 0:17.79 INFO | Using at most 32 threads.
 0:18.34 [6064] WARNING: Couldn't get the user appdata directory. Crash events may not be produced.: file c:\\mozilla-source\\toolkit\\crashreporter\\nsExceptionHandler.cpp, line 2158
 0:18.40 
 0:18.40 TEST-INFO | (xpcshell/head.js) | test MAIN run_test pending (1)
 0:18.41 
 0:18.41 TEST-INFO | (xpcshell/head.js) | test run_next_test 0 pending (2)
 0:18.41 
 0:18.41 TEST-INFO | (xpcshell/head.js) | test MAIN run_test finished (2)
 0:18.41 
 0:18.41 TEST-INFO | (xpcshell/head.js) | running event loop
 0:18.41 TEST-INFO | c:/mozilla-source/objdir-ff-debug/_tests/xpcshell/toolkit/components/filewatcher/tests/xpcshell/test_watcher.js | Starting dumb_test
 0:18.41 
 0:18.41 TEST-INFO | (xpcshell/head.js) | test dumb_test pending (2)
 0:18.42 
 0:18.42 TEST-INFO | (xpcshell/head.js) | test run_next_test 0 finished (2)
 0:18.42 
 0:18.42 TEST-INFO | (xpcshell/head.js) | test run_next_test 1 pending (2)
 0:18.42 
 0:18.42 TEST-INFO | (xpcshell/head.js) | test dumb_test finished (2)
 0:18.42 
 0:18.42 TEST-INFO | (xpcshell/head.js) | test run_next_test 1 finished (1)
 0:18.42 
 0:18.42 TEST-INFO | (xpcshell/head.js) | exiting test
 0:18.43 
 0:18.43 TEST-INFO | (xpcshell/head.js) | No (+ 0) checks actually run
 0:18.53 [6064] WARNING: Leaking the RDF Service.: file c:/mozilla-source/rdf/build/nsRDFModule.cpp, line 165
 0:18.57 [6064] WARNING: '!compMgr', file c:/mozilla-source/xpcom/glue/nsComponentManagerUtils.cpp, line 59
 0:18.57 [6064] WARNING: OOPDeinit() without successful OOPInit(): file c:\\mozilla-source\\toolkit\\crashreporter\\nsExceptionHandler.cpp, line 2588
 0:18.57 [6064] WARNING: XPCOM objects created/destroyed from static ctor/dtor: file c:\\mozilla-source\\xpcom\\base\\nsTraceRefcnt.cpp, line 143
 0:18.57 [6064] WARNING: XPCOM objects created/destroyed from static ctor/dtor: file c:\\mozilla-source\\xpcom\\base\\nsTraceRefcnt.cpp, line 143
 0:18.57 nsStringStats
 0:18.57  => mAllocCount:           2567
 0:18.57  => mReallocCount:          378
 0:18.57  => mFreeCount:            2567
 0:18.57  => mShareCount:           9125
 0:18.57  => mAdoptCount:            138
 0:18.57  => mAdoptFreeCount:        138
 0:18.57  => Process ID: 6064, Thread ID: 5584
 0:18.58 TEST-PASS | c:/mozilla-source/objdir-ff-debug/_tests/xpcshell/toolkit/components/filewatcher/tests/xpcshell/test_watcher.js | test passed (time: 776.000ms)
 0:18.62 INFO | Result summary:
 0:18.62 INFO | Passed: 1
 0:18.62 INFO | Failed: 0
 0:18.62 INFO | Todo: 0
 0:18.62 INFO | Retried: 0

Comment 1

[Kris Maglione [:kmag]]

Presumably fixed.

Comment 2

[Andrew McCreight [:mccr8]]

I don't think this is about RDF per se. RDF is just one place that apparently asserted if you leaked.

Comment 3

[Kris Maglione [:kmag]]

The only leak report shown in that output is for the RDF service. With the RDF service gone, nothing else to go on, and this bug being 4 years old, I'm not sure there's much point in keeping it open.

Comment 4

[Andrew McCreight [:mccr8]]

Well, there are specific steps to reproduce the leak given in comment 0.

I hacked up my local build to always log leak information to a file, and then added a new test to this directory and ran it (you have to update the generator syntax). We actually do leak a single nsTArray, but that sounds like a different issue. I also didn't see the message about RDF leaking (this is an m-c from about a week or so ago). Anyways, I guess closing it is fine after all.

Comment 5

[Kris Maglione [:kmag]]

(In reply to Andrew McCreight [:mccr8] from comment #4)
> I also didn't see the message about RDF leaking (this is an
> m-c from about a week or so ago).

That's because you and khuey fixed that warning about 4 years
ago in bug 1048435 :)