Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68442 > unrolled thread
| Started by | Jurko Gospodnetić <jurko.gospodnetic@pke.hr> |
|---|---|
| First post | 2014-03-17 18:53 +0100 |
| Last post | 2014-03-17 18:53 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: What does gc.get_objects() return? Jurko Gospodnetić <jurko.gospodnetic@pke.hr> - 2014-03-17 18:53 +0100
| From | Jurko Gospodnetić <jurko.gospodnetic@pke.hr> |
|---|---|
| Date | 2014-03-17 18:53 +0100 |
| Subject | Re: What does gc.get_objects() return? |
| Message-ID | <mailman.8209.1395078822.18130.python-list@python.org> |
Hi.
On 17.3.2014. 18:18, Antoine Pitrou wrote:
> All in all, though, gc.get_objects() is an expensive function call (it
> will walk the entire graph of objects tracked by the GC, which can be very
> large in non-trivial applications), so it's really only useful for
> debugging (and, I'd add, for low-level debugging). In most situations,
> gc.get_objects() is certainly the wrong tool to use.
I agree, and for the record, we were using it for debugging when I
started this thread - trying to track down a memory leak. :-)
gc.get_objects() turned out to be of great help with in resolving the
issue - in the end we tracked it down to a typical reference counting
problem in a Python extension DLL. *doh*
Best regards,
Jurko Gospodnetić
Back to top | Article view | comp.lang.python
csiph-web