Create a Post
Showing results for 
Search instead for 
Did you mean: 

SFWD process crash while viewing logs in WebUI

Soo, apparently it's possible to corrupt your log files if you start using an SD card for log storage on the 790 running R77.20.87 build 3004, if it already has some existing logs.

Not entirely sure how it started, but at some point, I was able to very consistently crash SFWD.

Reproduction was as easy as searching for blade:ips and then scrolling a bit down - probably triggering some parsing of corrupted log fields or something like that.

Running it in foreground with

fw sfwd -d

I was able to find four different crash messages.

*** Error in `fw': free(): invalid next size (fast): 0x050bdec0 ***
*** Error in `fw': malloc(): memory corruption: 0x050e14a8 ***
*** Error in `fw': munmap_chunk(): invalid pointer: 0x04058cb8 ***
terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_fill_insert

Of course the memory references were different each time.

After clearing the logs I wasn't able to reproduce. But I'll try to look again when the log amount is around the same as when I stumbled upon the crash.

In case you experience the log view UI crashing on you, copying off the logs, then clearing on the device might help you.

1 Reply

I suppose it is the same in latest jumbo (342) as well so may be open SR for TAC to investigate and possibly fix it.

0 Kudos


Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events