Quote:
It is probably just coincidence.
Yup, could be. It was me who wrote that on AW.net. It didn't freeze for a while after I installed the key file. However, a day later, I still noticed some freezes.
For my system, 2d or 3d mode doesn't matter. I'm using 3d mode currently.
As a workaround, I've disabled window dragging and resizing with full window contents and enabled double click on title bar in IControl. This reduces the number of repaint operations.
I experienced freezes while scrolling (esp. when there's lots of redrawing), and freezes when double-clicking on dock icons (two windows opened in quick succession).
I suspect it's in the window or layer management.
My Efika runs fine otherwise, as long as I don't click on anything, the machine doesn't freeze. Freezing occurs at random, during mouse-related operations.
The 3D screensaver works flawlessly. When it goes to stand-by mode (or black screen), the system wakes up correctly.
I have a Microsoft USB mouse attached at an external USB hub. I also tried a Logitech USB mouse, but that didn't work.
Sputnik seems to have a memory leak, after using it for a while (like, half an hour, or an hour) the system runs out of memory. After closing Sputnik, some of the memory reappears.
The system freezes when it runs out of memory.
MUI layouting is annoyingly slow. (for instance, it takes about one second to resize the MUIProcCalc window). Sputnik (which also seems to be using MUI) flickers a lot when updating pages. MUI scroll bars flicker. The flickering was of course a lot worse when using 2D mode, but in 3D it happens as well. The layouting/updating speed is about the same, though.
(p.s.: I don't know how MOS is implemented, but perhaps I could help fixing the bugs, I'm a developer myself, I have about 10 years of programming experience on Classic AmigaOS. In Classic AmigaOS, IIRC, the mouse driver delegates input events to a software interrupt handler chain, that in turn queues the events for Intuition using a message port. The interrupt handler must not call directly into Intuition. Classic Intuition doesn't wait indefinitely for a window event handler to complete, there is a timeout. The Classic RKRMs states that applications receiving mouse events shall collect as many as possible before acting on them. Since there's no such rule for resizing and moving windows, resizing and moving with full window contents should be done such that events are sent to the application only every 250 ms or so, and Intuition should not wait too long for the reply message to arrive. The layer locking mechnism should be thread safe and deadlock-proof. HTH)
(p.p.s: If GCC is used to compile MOS, I wouldn't use any 3.x versions, for they have many bugs in the optimizer. GCC 4.x is much better. Still, when optimization is used, I would check the assembly code for bugs. In a production release, the resulting assembly code should be checked for bugs. There's no currently cheap or free C/C++ compiler that is bug-free, all of them have bugs here and there.)
[ Edited by voyager2007 on 2008/7/4 5:08 ]
[ Edited by voyager2007 on 2008/7/4 5:17 ]