Description of Problem:
An attempt to start "Draw" on a machine with 128 Megs of memory on board
brought only an empty main window with an impossible to close
"No Response to Save Yourself ..." alert. Clicking on various buttons
and window controls of that alert resulted only in an appearance of the
second copy of the same alert and in a short time nothing was responding.
It was still possible to logon over a network and kill gdm restarting
everything. Less drastic attempts to regain a control, like killing
the application or a window manager, were not effective.
No other user application beyond basic session stuff was running at the same
I've this kind of problem with "writer" component two (tried also the rawhide
package)... I can just add that it hangs very often when using menus.
My computer is an athlon....
does this problem still appear with upgraded versions of OOo? Is it
possible to get a backtrace from OOo?
After such long time I do not have anymore a hardware in question
so I cannot try to run the same experiment. Nor I ever considered
Draw for a serious use so my experience with it is very limited.
But indeed with current hardware and current versions one can
draw at least something without instantly killing X.