[Libreoffice] Class Time and its funny ideas about time

[Terrence Enger]

Michael,

Sorry to be slow responding.  I have not been ignoring you
just for the sake of ignoring you.

On Thu, 2011-08-18 at 20:36 +0100, Michael Meeks wrote:
> Hi Terrence,
> 
> On Thu, 2011-08-18 at 14:27 -0400, Terrence Enger wrote:But of course, before creating bug 40273, I did a bug
search, finding bug 34769 "very slow after hibernate"
> > [snip]
> >               Is it still of interest?
> 
> 	Of course; LibO should never crash.

I suspect the cause may be like a couple of bugs which I
created and then marked INVALID; bug 40312 tells the story.
So, I am holding off on this one.

> 
> > [snip]
> >           Given my inability to make them happen again, are
> > they of interest?
> 
> 	Certainly; of course, if it is intermittent - it could well be memory
> corruption related;

I have created and then resolved INVALID,
(*) bug 40309 "SIGSEGV in Base, after clicking Queries
    button"
    <https://bugs.freedesktop.org/show_bug.cgi?id=40309>
(*) but 40312 "SIGSEGV closing Base"
    <https://bugs.freedesktop.org/show_bug.cgi?id=40309>

Short version: PEBCAK in that I forgot to source
install/program/ooenv.  At least, I do not know that I have
seen a SEGV after I did source ooenv.

Meanwhile, I have asked on the discussion list whether LO
should be more helpful in the face of an error like this.

>                     if you can bear the 50-fold performance hit -
> running under valgrind would be time well spent; ensure you:
> export G_SLICE=always # first though. That may well give you accurate
> data for the real bug; how well it works with java-ness is unclear
> though.

Extrapolating from Caolán's answer to another of my
questions, I tried valgrind to look at the first of these
SEGVs.  Two hours later, I was nowhere near the point of
(previous) failure.  I gave up.

> 
> 	Very good of you to continue chasing it; 

Heh, heh, heh.

Along the way to reporting the first SIGSEGV, the one which
I am holding back, I wanted to print an excerpt from the
notes I made at the time.  This led to bug 40258 "Writer
PRINTING a paragraph like following list"
<https://bugs.freedesktop.org/show_bug.cgi?id=40258>,

But of course, before creating bug 40258, I wanted to try
the same printing with my local build.  The result is bug
40237 "crash, SIGPIPE after suspend/resume or switch users"
<https://bugs.freedesktop.org/show_bug.cgi?id=40237>.

But of course, before creating bug 40273, I did a bug
search, finding bug 34769 "very slow after hibernate"
<https://bugs.freedesktop.org/show_bug.cgi?id=34769> and
ubuntu bug 606558 "switching user while Compiz enabled make
OpenOffice.org crawl (extremely slow scrolling)"
<https://launchpad.net/bugs/606558>.  That would have been
okay, except that I got caught up in the suspicion that
suspend/resume contributed to my SEGVs.  I wasted quite some
time on that with entirely negative results.

>                                                and of course much of the
> database stuff is -really- hard to get setup and/or test meaningfully. I
> keep hoping for Wols to finish the sqlite backend and to get that
> integrated, so we can do some fast/native unit tests for database bits.

Before very long, I shall have to learn about unit test.  At
least, I hope that I shall have to.


Thanks,
Terry.