Sparkle

NSURLConnection leaks

Bug #228449 reported by Andy Matuschak on 2008-05-09

Affects		Status	Importance	Assigned to	Milestone
	Sparkle	Fix Released	Medium	Unassigned	Sparkle 1.5

Bug Description

I just did some leak hunting in my own app (which incorporates Sparkle) and saw that Sparkle did leak some NSURLConnect stuff. Turns out that sometimes "NSURLConnect sendSynchronousRequest:" can have a tendency to leak memory when used in multithreaded environments. It is usually advised to use the asynchronous version, which doesn't seem to leak.

More info [http://www.cocoadev.com/index.pl?MemLeaksWithMultiThreadNSURLConnection here] and keep up the good work!

This ticket was migrated from the old trac: re #24
Originally reported by: Wouter

See original description

Related branches

lp:sparkle

Andy Matuschak (andymatuschak) on 2008-05-09

Changed in sparkle:
importance:	Undecided → High
milestone:	none → 1.5
status:	New → Confirmed
description:	updated
Changed in sparkle:
importance:	High → Medium

Andy Matuschak (andymatuschak) on 2008-05-14

Changed in sparkle:
status:	Confirmed → Fix Committed

Andy Matuschak (andymatuschak) on 2008-06-02

Changed in sparkle:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.