Re: crm failing on a specific email

[email protected] Thu, 15 Sep 2011 09:02:11 -0400
Newsgroups gmane.mail.spam.crm114
Message-ID <[email protected]>
Jason Lewis <[email protected]> writes:

Jason:

Those windows are very small.  

The _default_ window is something like 2 megabytes.

Try upping it to 64 megs or so - i.e. "-w 64000000"

    - Bill Yerazunis



> [email protected] wrote:
>
>> That only limits the amount of stuff that is tokenized and
>> fed into the classifier (IIRC).  The initial read-in is still
>> limited by the windowsize- and again IIRC, the isolation buffer is
>> still a fixed ratio of the windowsize as well.
>> 
>> But this is... still interesting.
>> 
>> Does making the -w (windowsize allocation) larger help at all?
>> 
>> Or do we have a much more interesting bug?
>> 
>>    - Bill Yerazunis
>
> A few tests follow:
>
> jason@debian:~/.crm114working$ crm -w 8192 -t mailreaver.crm --spam <
> ../1315543615.M799816P25984V000000000000FD00I0000000000020F4B_19.debian\,S\=4324304\:2\,S
> Setting usertrace level to 1
> Using program file mailreaver.crm
> Commandline set of user variable at 5 '--spam'.
> Loading program from file mailreaver.crm
> Hash of program: FFFFFFFFBCCCCA88, length 22671 bytes
>
>  Setting cmdline var ':spam:' to 'SET'
> Inserting file 'maillib.crm' .
> Program statements: 1170, program length 37134
>
> crm: *ERROR*
>  This program has overflowed the ISOLATEd data area with a variable
> that's just too big.  The bad variable was named:  :_pgm_text:
>  Sorry, but this program is very sick and probably should be killed off.
> This happened at line 1169 of file mailreaver.crm
> The line was:
> --> <--
>
> Then I upped the window to 65536 and got this error:
> .....
> .
> .
> vB4j51GehH3tRnlW/ARZoJ8iTSb3se6nRk/CTjka4z4K92XY5dbR65j/yZt2+T72vLgb47LvgC7e
> Pt+wxdG3fraMdcTmcfLGmenr7cJ0gXkdp2+MC5vHRa6TMyklx7k/zd3F5Ih7n0WfV5i9MpvhpnI9
> DjbGdMTel/6AtJk9Yn4fyr2Kd90LfTxFFoVw9LpwK3Bn9+in9EtkfmxX74csWyQYym7wvMZRLVyb
> +0Ju9PRv7rxj4aUngjtbDIYp83fuCeHDQLw8sT+fz/FE4HiSXb56GYfs8tSajhEZSWRET3Bk+QlK
> rhPhwz956AmePbEdXvOAM
> Parsing line 663 :
>  -->  output /:*:_nl: Aw, crud.  mailreaver.crm broke.  Here's the
> error: :*:\_nl:/
>
>
> Executing line 663 :
>  Executing an OUTPUT statement
>   filename >>><<<
>   pre-IO seek to >>><<< --> 0
>   and maximum length IO of >>><<< --> 65536
>
>  Aw, crud.  mailreaver.crm broke.  Here's the error: :\_nl:
> Parsing line 664 :
>  -->  output /:*:broken_program_message:/
>
>
> Executing line 664 :
>  Executing an OUTPUT statement
>   filename >>><<<
>   pre-IO seek to >>><<< --> 0
>   and maximum length IO of >>><<< --> 65536
>
> crm: *ERROR*
>  You have blown the memory-storage gaskets while tryingto store the
> ISOLATEd variable  :in_text:oo
>  Sorry, but this program is very sick and probably should be killed off.
> This happened at line 204 of file mailreaver.crm
>
> Parsing line 665 :
>  -->  output [stderr] /:*:_nl: ERROR: mailreaver.crm broke.  Here's the
> error\: :*:_nl:/
>
>
> Executing line 665 :
>  Executing an OUTPUT statement
>   filename >>>stderr<<<
>   pre-IO seek to >>><<< --> 0
>   and maximum length IO of >>><<< --> 65536
> Opening file stderr for I/O (writing)
>
>  ERROR: mailreaver.crm broke.  Here's the error\:
>
> Parsing line 666 :
>  -->  output [stderr] /ERROR: :*:broken_program_message:/
>
>
> Executing line 666 :
>  Executing an OUTPUT statement
>   filename >>>stderr<<<
>   pre-IO seek to >>><<< --> 0
>   and maximum length IO of >>><<< --> 65536
> Opening file stderr for I/O (writing)
> ERROR:
> crm: *ERROR*
>  You have blown the memory-storage gaskets while tryingto store the
> ISOLATEd variable  :in_text:oo
>  Sorry, but this program is very sick and probably should be killed off.
> This happened at line 204 of file mailreaver.crm
>
> Parsing line 667 :
>  -->  }
>
>
> Executing line 667 :
> Statement 667 is a closebracket. depth now 0.
>
> Parsing line 668 :
>  -->  exit /:*:program_fault_exit_code:/
>
>
> Executing line 668 :
> Exiting at statement 668 with value 1
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop 
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops?   How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> _______________________________________________
> Crm114-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/crm114-general

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/