Hi Chris!
Ok, Magnus managed to isolate the "Processes going wild"-bug. To make sure you get a chance to debug this we simply froze the whole Gjallar installation! :) It is available here:
http://gjallar.krampe.se/gjallar_before_clean_image_small.zip (53 Mb)
Mmm, that is for windows, eh, well - it probably can be opened on another box too.
Here follows the step by step instruction from Magnus: ------------ To reprocude the problem where Gjallar runs an infinite(?) loopŸspawning thousands of processes, follow these instructions.
1. Unzip theŸ53Mb file.
2. Open the image: "Squeak3.8-6665-gjallar.6.image" (Wait for the web server to start)
3. In a web browser navigate to: http://localhost:8081/seaside/Gjallar
4. Log in as: root/goldfish
5. Proceed over the break points at: ŸŸŸ - Q2RootUser(Q2User)>>tabelCaseForm ŸŸŸ - Q2RootUser(Q2FullAccessUser)>>processes
6. When proceeding over Q2Model>>processes, new processes (threads) will be spawned like crazy...
7. To stop the creation of new processes. ŸŸŸ - In the Workspace named "Doits", run the code: ŸŸŸ (Process allInstances select: [:p | p isSuspended]) do: [:pp | pp terminate; install: nil ] ŸŸŸ - Repeat (hit alt-d over and over) until a new debugger window pops up (MessageNotUnderstood: UndefinedObject>>realObjectFor:)
8. When all suspended processes are killed, navigate to http://localhost:8081/seaside/Gjallar, and log is as balder/balder. This works fine, because this user will use the Q2User instance variable for self processes. The root user uses self model processes.
/ Magnus