[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

James G. sack (jim) added the comment: IMPORTANT Correction: Please disregard msg 96468 & 96470. I was forgetting to do ./configure and make, and evidently getting bogus failures. test_codecs works fine now, ..sorry for the false alarm. ~jim -- _

[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

James G. sack (jim) added the comment: Clarification of my last message (msg96468): The test_handler in the current revision (76850) also exhibits the same memory-gobbling behavior. I only refered to -r 74869 because that's where the test was introduced, ostensibly to verify the patch to uni

[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

James G. sack (jim) added the comment: It seems that on my Fedora 11 AMD X86_64, the problem still exists. In test_codecs.UTF32Test, test_handlers() seems to run forever, gobbling memory to 99+% and then activating swap until it fills up swap. tested by svn up -r 74869 rm /tmp/pynexttest

[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

Georg Brandl added the comment: I'm leaving a refactoring to someone with more time :) Committed in r74869, backported to 2.6 in r74870. -- status: open -> closed ___ Python tracker ___

[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

Marc-Andre Lemburg added the comment: The patch looks good. Thanks. Aside: This is what you get when using too many single character variable names in a function... The function should really do just one cast to (unsigned char *) at the very top and then work with that variable all along. ---

[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

Georg Brandl added the comment: This patch fixes it (seems like a refactoring oversight, I used the UTF16 decoder for reference, where it works fine) and adds a test, assigning to MAL for review. Marking as a release blocker so that 2.6.3 won't get released without a fix. -- assignee:

[issue6922] Interpreter hangs up while trying to decode invalid utf32 stream.

New submission from Alex : *** Prerequisites: Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 *** Description: 'utf_32_le' and 'utf_32_be' codecs are overconsuming memory when input data are damaged and kwarg 'errors' to str.decode is other than 'strict'. *