Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #48228

Re: Debugging memory leaks

Show all headers | View raw

On Fri, Jun 14, 2013 at 11:53 PM, rusi <rustompmody@gmail.com> wrote:
> On Jun 14, 1:15 am, Giorgos Tzampanakis
> <giorgos.tzampana...@gmail.com> wrote:
>> Am I the only one who thinks this is terrible advice?
>
> I would expect a typical desktop app to run for a couple of hours --
> maybe a couple of days.
> Living with a small (enough) leak there may be ok.
> [In particular I believe that most commercial apps will leak a bit if
> run long enough]
>
> The case of something server-ish is quite different.
> A server in principle runs forever.
> And so if it leaks its not working.

I keep my clients running for months. My Windows laptop (let's not
even get started on my Linux boxes) got rebooted a few weeks ago
(can't remember why), but I've had it running for two months or more
at a time. And that's Windows XP, not the most stable OS ever
invented, and a computer that's used fairly constantly - two web
browsers, a MUD client that retains full history, music/movie playing
with VLC, SciTE, IDLE, BitTorrent, and a bunch of other stuff. And I
don't reboot it; I don't even restart applications if I can help it
(except VLC, I tend to close that when I'm done). Any memory leak in
any of the apps I use would be highly visible and extremely annoying;
and there *were* such leaks in the Flash players of yesterday.
Fortunately now I can leave browsers running constantly. (Either that,
or the plugins container gets restarted. Not sure.)

Just because it's a client doesn't mean it can't be treated seriously. :)

Of course, my style IS unusual. Most people don't do what I do.

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Debugging memory leaks writeson <doug.farrell@gmail.com> - 2013-06-12 18:24 -0700
  Re: Debugging memory leaks dieter <dieter@handshake.de> - 2013-06-13 08:29 +0200
    Re: Debugging memory leaks Giorgos Tzampanakis <giorgos.tzampanakis@gmail.com> - 2013-06-13 20:15 +0000
      Re: Debugging memory leaks Steve Simmons <square.steve@gmail.com> - 2013-06-13 22:45 +0100
      Re: Debugging memory leaks Chris Angelico <rosuav@gmail.com> - 2013-06-14 08:36 +1000
      Re: Debugging memory leaks Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-06-14 02:40 +0000
        Re: Debugging memory leaks Chris Angelico <rosuav@gmail.com> - 2013-06-14 19:30 +1000
        Re: Debugging memory leaks Giorgos Tzampanakis <giorgos.tzampanakis@gmail.com> - 2013-06-14 22:57 +0000
          Re: Debugging memory leaks Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-06-15 01:39 +0000
        Re: Debugging memory leaks dieter <dieter@handshake.de> - 2013-06-15 08:52 +0200
        Re: Debugging memory leaks Chris Angelico <rosuav@gmail.com> - 2013-06-15 17:21 +1000
        Re: Debugging memory leaks dieter <dieter@handshake.de> - 2013-06-16 08:18 +0200
      Re: Debugging memory leaks rusi <rustompmody@gmail.com> - 2013-06-14 06:53 -0700
        Re: Debugging memory leaks Chris Angelico <rosuav@gmail.com> - 2013-06-15 10:11 +1000
        Re: Debugging memory leaks Ben Finney <ben+python@benfinney.id.au> - 2013-06-15 10:16 +1000
          Re: Debugging memory leaks rusi <rustompmody@gmail.com> - 2013-06-14 20:16 -0700
            Re: Debugging memory leaks Ben Finney <ben+python@benfinney.id.au> - 2013-06-15 21:23 +1000
              Re: Debugging memory leaks rusi <rustompmody@gmail.com> - 2013-06-15 04:35 -0700
                Re: Debugging memory leaks Chris Angelico <rosuav@gmail.com> - 2013-06-15 21:54 +1000
  Re: Debugging memory leaks writeson <doug.farrell@gmail.com> - 2013-06-13 11:07 -0700
    Re: Debugging memory leaks Dave Angel <davea@davea.name> - 2013-06-13 14:44 -0400
  Re: Debugging memory leaks rusi <rustompmody@gmail.com> - 2013-06-14 05:36 -0700
  Re: Debugging memory leaks "Frank Millman" <frank@chagford.com> - 2013-06-21 08:50 +0200

csiph-web