➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: python code fails with "MemoryError" on HP-UX 11.11 PA_RISC
Type: Stage:
Components: Interpreter Core Versions:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: loewis, shashikala
Priority: normal Keywords:

Created on 2007-03-01 04:27 by shashikala, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
Pythonmemoryerror.txt shashikala, 2007-03-01 11:47
Messages (6)
msg31389 - (view) Author: shashi (shashikala) Date: 2007-03-01 04:27 
Hi,

 Python-2.5 code fails with "MemoryError". This is happening only on one system, PA-RISC running HP-UX 11.11.Failing system has 12 GB of RAM installed, non-failing system has 8 GB.

1) spark 9GB phys mem(Python is working fine)
2) stalker 12GB phys mem (that has problem with python 2.5 )


please assist me in this.

Thanks in advance
Shashi
msg31390 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2007-03-01 06:38 
This tracker is not about assistance. If at all, we need you to assist us.

Can you please report more details, like stack traces, causes of the crash, patches? If not, I think there is little we can do about this report ("it crashes" is pretty unspecific).
msg31391 - (view) Author: shashi (shashikala) Date: 2007-03-01 11:47 
File Added: Pythonmemoryerror.txt
msg31392 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2007-03-01 21:34 
Can you also provide a gdb/dbx backtrace of where the problem occurred?
msg31393 - (view) Author: shashi (shashikala) Date: 2007-03-08 03:57 

 Hi ,

 I added "import gc" and "gc.collect()" , it worked out fine , I dint get any further  MemoryError  is this the correct approach , please let me know about the same. 

Thanks and Reagrds,
shashi
msg31394 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2007-03-08 09:19 
If you think your problem is solved, then fine (you seem to have found a work-around).

If Python raises a MemoryError, this is still a problem; it sholdn't normally do that, and it should normally invoke garbage collection itself. To analyse this further, we still would need a debug stack trace. However, I'm closing this as "won't fix" now; if you ever feel like analysing it further, and have data to help there, feel free to reopen the report.
History
Date User Action Args
2022-04-11 14:56:22adminsetgithub: 44640
2007-03-01 04:27:29shashikalacreate