Can anyone else on Windows duplicate either of these sets of
symptoms
(deliberately using up memory for the former, or following Josh's instructions for the latter)?
cant reproduce the first one, ran some big images through the tracer, loaded several large video files so my system was out of physical memory, and it worked fine (if rather slowly.) Without more precise conditions I cant do much more.
Ok, when working on the tutorials Inkscape got "uber-funked" ~15 times. It is always when I am working with text objects. All I can recommend is to grab the one of the larger tutorials I uploaded and mess around. Move text boxes, edit some text, etc. Occasionally hop into another program and hop back as well as I always multitask and just want to cover all bases. It has done it in every Win32 build for the past couple weeks, on multiple systems. An interesting thing is that the window that starts spazzing/becomes non-responsive (and makes the log go nuts) doesn't seem to affect other open Inkscape windows (within the same process). And for note this is usually after ~20-30 mins of editing a document.
I don't quite understand the process for gdb, so I haven't been able to pull any good information other than what inkscape's log window says. Due to the frequency of me bringing it down, I have to recommend we try to get it fixed before release. I will file a bug report on it once I can reproduce it on demand. Otherwise, gdb will be the way to track it down, huh?
-Josh