Tue Sep 13 07:38:03 PDT 2005
- Previous message: [Slony1-general] "realloc() - Cannot allocate memory" errors
- Next message: [Slony1-general] "realloc() - Cannot allocate memory" errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Output is attached...let me know if you want me to run it for longer... Darcy Buskermolen wrote: >On Monday 12 September 2005 00:16, Philip Warner wrote: > > >>Philip Warner wrote: >> >> >>>2005-09-12 12:22:14 EST FATAL dstring_addchar: realloc() - Cannot >>>allocate memory2005-09-12 12:22:14 EST DEBUG1 slon: shutdown requested >>> >>> >>Further to this; the virtual mem size of the process is about half a gig >>when it dies...so it looks like some kind of leak. >> >> > >is there any possibility you could run this under valgrind and report what you >see? > > _______________________________________________ Slony1-general mailing list Slony1-general at gborg.postgresql.org http://gborg.postgresql.org/mailman/listinfo/slony1-general -------------- next part -------------- A non-text attachment was scrubbed... Name: valgrind.log.gz Type: application/x-gzip Size: 20622 bytes Desc: not available Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050913/3e1c46ee/valgrind.log-0001.bin
- Previous message: [Slony1-general] "realloc() - Cannot allocate memory" errors
- Next message: [Slony1-general] "realloc() - Cannot allocate memory" errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list