I just had a strange thing happen:

I have a pretty big spreadsheet (.ods): 3 pages x 250,000 cells in each, plus maybe 50,000 graphic objects (simple rectangles). But it used to open in OOo Calc 2.0.2 in about 1.5 minutes, and I can live with that.

But sometime yesterday (not sure exactly when) I did something (not sure exactly what) and everything slowed to a crawl. It took a full minute after a right mouse click for a menu to draw. (I'm not exaggerating.)

It took 3 minutes to paste a copy of one cell into another cell.

It took 7 minutes to go from one sheet to another.

It took 93 minutes to save the file. (I waited for it a while, gave up, went to the grocery store, it was still crunching away when I got back.)

It took 9 minutes to quit the program.

It took 40 minutes to restart and re-open the file. (I didn't think to stop and restart the QuickStarter, maybe I should have.)

I opened up the Windows TaskManager, and during all of this there was almost no CPU activity at all, but the disk was thrashing like crazy. 15 million page faults.

I shut down the program again and did a disk defrag. (But still didn't restart the QuickStarter.) Made no difference.

I decided to reboot. During the shutdown, Windows said a couple of programs weren't responding:

"Xprt message" something-or-other;
"DDE server" something-or-other;
"soffice.bin"

After the reboot, everything seems to be back up to speed. For comparison: 150K page faults.

So a couple of questions:

What's the difference between soffice.exe and soffice.bin? While I was using the program, it was soffice.exe that was racking up the CPU time and page faults, so what's soffice.bin?

Are "Xprt message" thingy and "DDE server" thingy components of OOo, or are they Windows components?

Do Xprt or DDE give anyone any ideas what I should try *not* to do again in the future?

System:
Windows XP
OOo 2.0.2





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to