Dear Patrick,

Am Donnerstag, den 25.06.2015, 18:25 +0200 schrieb Patrick Wacker:

> I'm the upstream author of AB-Transfers. Thank you for your detailed 
> explanations.

Thank you for writing AB-Transfers!

[…]

> > Looking at the “bad” `history.ctx` it’s size is 41 MB (42626560 
> > Bytes) and I think it contains strange characters due to umlauts I 
> > put into the “Verwendungszweck” with the middle click as it’s not 
> > allowed (for some reason) entering it with the keyboard.
> During development I had some issues with the German umlauts. Some 
> banks supported it some don't.
> And also the aqbanking backend sometimes replaced some umlauts with 
> spaces or not readable characters (but a crash did not happened).
> Therefore I decided to be on the save side and disabled the input of 
> umlauts at abtransfers (didn't blocked/checked copy&paste input, my 
> fault).

The Berliner Volksbank seems to support it. I guess this is a bug in
AqBanking then.

> Also a size of 41 MB is pretty big, either you using the program for 
> a long time with a lot of transfers or something else is wrong. A 
> normal transfer should occupy around 1.2 KB at the history (>34000 
> transfers needed to reach 41MB).
>
> > Also looking at `history.ctx` after the crash yesterday, the format
> > seems to be incorrect. The following is missing at the end of the 
> > file
> > compared to the file written today.
> > 
> >             int  cycle="0"
> >             int  executionDay="0"
> >             char type="transaction"
> >             char subType="none"
> >             char status="none"
> >             char charge="Nobody"
> >             char sequenceType="once"
> >           } #transfer
> >         } #transferList
> >       } #accountInfo
> >     } #accountInfoList
> > 
> A few lines above this missing entries (or directly at the end) of 
> your "bad" history.ctx file should be a line starting with "char 
> purpose=".
> 
> Could you remember which purpose (with umlauts) do you used?

The last line in the “after crash” file is the following (without the
closing ").

    char period="none

It’s a transfer from last November.

> Which is the character that could not be written at the "bad" 
> history.txt and maybe caused the crash?
> 
> If I know this I could try to reproduce it here and maybe could fix 
> it.

The name of the account has umlauts in it: SG Friedrichshain Grün-Weiß
90 e. V..

Looking at the newly written `history.ctx` with only three
transactions, it looks like the umlauts are recoded during each write.
(The most recent entry is at the top.)

    char localName="SG Friedrichshain Gr%C3%BCn Wei%C3%9F"
    char category="JobStatus%3A 5", "JobType%3A 16"

    char localName="SG Friedrichshain Gr%C3%83%C2%BCn Wei%C3%83%C2%9F"
    char category="JobStatus%3A 5", "JobType%3A 16"

    char localName="SG Friedrichshain Gr%C3%83%C2%83%C3%82%C2%BCn 
Wei%C3%83%C2%83%C3%82%C2%9F"
    char category="JobStatus%3A 5", "JobType%3A 16"

So with not a big number of transaction, that file gets pretty big as
the `localName` lines get bigger after each transaction. In the faulty
file the longest line has 12582962 columns.

This probably causes the assertion in libgwenhywfar60 4.14.0-1.

    3:2015/06/22 08-46-31:gwen(11198):buffer.c:  314: Size is beyond hard limit 
(16777274>16777216)

(Is the whole transfer block read in at once?)


Thanks,

Paul

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to