Hello,
This is my very first email, so let me introduce myself. I am Ivan Rojas, student at the University of Chile. As my first project in Pharo and Seaside, I am working on a server that compute metrics (same spririt than Hudson, but more general and with a nicer output).
I am stuck on a problem that appears for the second time. When I open my image, I get the message:
"Warning: Pharo is almost out of memory!
Low space detectionis now disabled. It will be restored when you
close or proceed from this error notifier. Don´t panic, but do proceed
with caution."
Nothing can be done after that (I tried alt-. but no success).
My configuration is
- Seaside-3.0.3-OneClick
- Windows 7
Any suggestion?
Cheers,
Ivan
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
that could happen if you have a recursion problem.
if that's the case them you should have in an piece of your code with something like: initialize self initialize. "<-- note self instead of super" then it'll eat up your RAM and you will feel the UI become as liquid as solid honey (to put it delicately) what can you do? 2. kill that process (with activity monitor or task manager or sudo kill -9 pid) then open it again and recover lost changes 3. if you have the patience to navigate the solid honey UI you can try to open a process browser and check the seaside threads, one of them may be the one eating all up (try debugging it with cmd-d) On Dec 23, 2010, at 4:31 PM, ivan rojas wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by ivan rojas
On Thu, Dec 23, 2010 at 7:31 PM, ivan rojas <[hidden email]> wrote:
Excellent, congratualtions!
So...the first time, you can run the image, you save it, and when opening again, you get that message? which is the size of the image on disk once you save it ? As Sebastian said, most of the times this error is due to a recursion :( do you have a PharoDebug.log ? if true, attach it. It's a pity it is on startup, because otherwise there may be other things you can do. For example, you may be able to start a CPUWatcher and see if there is a process that takes a lot of CPU (if it is a recursion it may probably take not only a lot of memory but also cpu). Cheers Mariano
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |