[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: Overloading the Memory when laying out a ballot

Okay, this database does illustrate the leak very handily.  1.17 has the same problem, 1.11 is okay.  This one will take some time to track down.
 
Ken
 
 
-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Greg Forsythe
Sent: Monday, August 13, 2001 1:17 PM
To: bugtrack@dieboldes.com
Subject: Re: Overloading the Memory when laying out a ballot

This is the database.  I should have stopped and saved.
----- Original Message -----
From: Ken Clark
Sent: Monday, August 13, 2001 3:43 PM
Subject: RE: Overloading the Memory when laying out a ballot

Not enough to reproduce here.  I just dragged a dozen headers onto a ballot;  no serious increase in memory usage.  Anyone else seeing Greg's behavior?
 
Ken
 
 
 
-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Greg Forsythe
Sent: Monday, August 13, 2001 12:38 PM
To: Bugtrack
Subject: Overloading the Memory when laying out a ballot

GEMS-1-18-3
 
When laying out a ballot containing a lot of drag on headers, it is necessary to save continuously. 
 
The consequences are a system message that says you are running out of memory, GEMS crashes and you lose all the work. 
 
Could there be a warning to save as opposed to complete loss of work?

Greg Forsythe
Global Election Systems, Inc
(416) 446-1383 office   (416) 446-1425 fax
(416) 464-3736 cell
www.dieboldes.com