Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Crash report involving propagate and replies, posted by Stephen on Tue Nov 26 16:24:39 2013 elogd.cfg
    icon2.gif   Re: Crash report involving propagate and replies, posted by David Pilgram on Tue Nov 26 21:49:42 2013 
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Wed Nov 27 15:22:37 2013 
    icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Dec 2 09:27:35 2013 elogd.cfg
    icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Dec 2 09:58:42 2013 elogd.cfgelog.png
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Mon Dec 2 23:02:45 2013 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Tue Dec 3 11:30:43 2013 
             icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Fri Jan 3 21:33:40 2014 error1.jpgerror2.jpgerror3.jpg
                icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 6 10:25:03 2014 
                icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Jan 6 10:32:43 2014 
                   icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Sun Jan 12 04:48:12 2014 test.jpgtest2.jpg
                      icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 13 09:01:31 2014 
    icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 13 09:30:09 2014 
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Fri Jan 24 18:59:17 2014 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Wed Jan 29 17:13:55 2014 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Mon Feb 3 22:45:10 2014 
Message ID: 67649     Entry time: Mon Jan 13 09:30:09 2014     In reply to: 67628     Reply to this: 67659
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: Windows  ELOG Version: 2.9.2 
Subject: Re: Crash report involving propagate and replies 

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies.  On the 10th reply the application crashed, this is repeatable 100% of the time.  Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?

/Stefan 

ELOG V3.1.5-3fb85fa6