SAC Developers

A forum for SAC developers to exchange ideas about SAC enhancements, bug fixes, etc.

Email address
sac-dev@lists.ds.iris.edu
Type
Subscribers
178
Moderated by
IRIS Webmaster
Related tags
None
March
February
January
December
November
October
September (1)
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June (2)
May
April
March
February
January
December
November
October (3)
September
August
July (1)
June
May
April
March
February
January
December (1)
November
October
September
August
July
June
May
April (2)
March
February (1)
January (2)
December
November (1)
October
September (2)
August (1)
July
June (11)
May
April
March
February
January
December
November
October
September
August
July
June
May
April (1)
March
February
January
December
November
October
September
August (2)
July
June
May (1)
April (1)
March (1)
February
January
December
November
October
September
August
July
June (2)
May
April
March (2)
February (5)
January

Active Message Threads for August 2011

Mark Wiederspahn
2011-08-19 23:26:23
Dear sac-dev, A user here was reading in ~400MB month-long data files into sac 101.3b, and ran out of swap space. I looked at the behavior on both rhel4 linux and solaris8, and it is similar. "Read" opens the input file, reads the header, closes the file, opens it again and re-reads the header, mallocs space for the trace, and then reads that. I don't see any place where it free's the malloc'ed memory, and each malloc result address is different. On subsequent "read file"'s it never seems to… [more]
No replies
17:13:26 v.01697673