Issue 4568066: Fix possible resource leak in AtomicCounterWithMutex

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Can't Edit
Can't Publish+Mail
Start Review

Created:
14 years, 3 months ago by Yuryu

Modified:
14 years, 3 months ago

Reviewers:

CC:
googletestframework_googlegroups.com

Base URL:
http://googletest.googlecode.com/svn/trunk/

Visibility:
Public.

Created: 14 years, 3 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -0 lines)			Patch
	M	test/gtest-port_test.cc	View		1 chunk	+1 line, -0 lines	0 comments	Download

Total messages: 1

Yuryu

14 years, 3 months ago (2011-06-09 10:28:06 UTC) #1

In this test, it initializes a mutex but doesn't destroy it.
This causes a problem on QNX.