[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #12962: fflush Crash in BFS
From:       "AGMS" <trac () haiku-os ! org>
Date:       2016-09-25 22:59:23
Message-ID: 055.51009b99833b26e7e76bd51daae534c1 () haiku-os ! org
[Download RAW message or body]

#12962: fflush Crash in BFS
--------------------------------+----------------------------
   Reporter:  AGMS              |      Owner:  axeld
       Type:  bug               |     Status:  new
   Priority:  normal            |  Milestone:  Unscheduled
  Component:  File Systems/BFS  |    Version:  R1/Development
 Resolution:                    |   Keywords:  fflush
 Blocked By:                    |   Blocking:
Has a Patch:  0                 |   Platform:  All
--------------------------------+----------------------------

Comment (by AGMS):

 It's quite likely that it's running out of memory, since we often see
 other programs (like SoundPlay) consuming hundreds of megabytes (there's a
 logging program monitoring the other ones, once per second, kind of
 annoying that it triggers the crash when writing the log).  I'll see if I
 can get a syslog the next time it crashes, though if the file system
 crashes while writing, that may not work for detecting the error :-)

 Is there an API for getting the available and free memory totals?  It
 would be useful to see if it's getting close shortly before the crash.
 The kernel system info just has a page count, which isn't actually memory
 used, I assume.  I did use counting up the sizes of areas for particular
 program teams to find the memory used by a program, guess I could do that
 for all teams.  Wonder if that's what ProcessController does...

--
Ticket URL: <https://dev.haiku-os.org/ticket/12962#comment:3>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.

[prev in list] [next in list] [prev in thread] [next in thread]