Perhaps to a Mantis report?

On Mon, May 3, 2010 at 10:50 AM, Hannes Hirzel <hannes.hirzel at gmail.com> wrote:
> Hello
>
> I have found a 110kB sample jpg file which causes the MSWindows VM to
> crash immediately *** whereas it displays the file properly under
> Ubuntu.
>
> I will happily sent the file to anybody interested having a look at this....
>
> --Hannes
>
> ***
> # Debug console
> # To close: F2 -> 'debug options' -> 'show output console'
> # To disable: F2 -> 'debug options' -> 'show console on errors'
> Corrupt JPEG data: 1 extraneous bytes before marker 0xd9
>
>
> On 5/3/10, Baveco, Hans <Hans.Baveco at wur.nl> wrote:
>> You're right, with the following the VM immediately crashes (reading
>> just 3 files):
>>
>> | dir files slash |
>>  dir := 'f:\squeak3'.
>>  files := (FileDirectory on: dir)  fileNamesMatching: '*.jpg'.
>>  slash := FileDirectory slash.
>>  ^files collect: [:each | ImageReadWriter formFromFileNamed: dir , slash
>> , each].
>>
>> Hans
>>
>>
>>
>>
>> Am 29.04.2010 10:55, schrieb Hannes Hirzel:
>>> Some jpg files cause this. Most of the jpg files don't.
>>>
>> I've noticed this as well, but only under windows.
>> Maybe the JPEG reader plugin has some memory problems (buffer overflow?
>> - C functions are always suspicious).
>>
>> I wonder whether it could be reproduced without the image-in-filelist
>> hack, i.e. by simply opening several jpeg files in a row.
>>
>> Cheers,
>> Hans-Martin
>>
>>
>>
>>
>
>