Issue 97220 - Crash with Before record action form event macro
Summary: Crash with Before record action form event macro
Status: CLOSED OBSOLETE
Alias: None
Product: App Dev
Classification: Unclassified
Component: scripting (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: Unknown Linux, all
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-12 23:07 UTC by etfloyd
Modified: 2017-04-04 16:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Small ODB to reproduce Before Record Action event crash (12.81 KB, application/vnd.sun.xml.base)
2008-12-12 23:10 UTC, etfloyd
no flags Details
java error report (113.92 KB, text/plain)
2008-12-13 23:01 UTC, drewjensen.inbox
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description etfloyd 2008-12-12 23:07:54 UTC
Crash occurs on "Before record action" event on a form with any macro bound to
that event under Linux. I have reproduced this on OOo 3.0 and 2.4.1 on Ubuntu
8.04 and 9.10. The crash does not occur on Windows XP. I have a small .odb that
demonstrates the problem.
Comment 1 etfloyd 2008-12-12 23:10:33 UTC
Created attachment 58791 [details]
Small ODB to reproduce Before Record Action event crash
Comment 2 etfloyd 2008-12-12 23:17:00 UTC
(*Occurs on Ubuntu 8.04 and 8.10)

To reproduce crash, open attached .ODB and run Form1, update a row.
Comment 3 drewjensen.inbox 2008-12-13 22:57:46 UTC
Was able to reproduce this crash using OOO300_m13 and DEV300_m37 under Ubuntu
8.10 (x64)

Running from a term produces this output

An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f291c3dc32e, pid=8637, tid=139814947948272
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b15 mixed mode linux-amd64)
# Problematic frame:
# C  [libgcc3_uno.so+0x332e]

attaching error log
Comment 4 drewjensen.inbox 2008-12-13 23:01:50 UTC
Created attachment 58802 [details]
java error report
Comment 5 kay.ramme 2008-12-15 08:16:50 UTC
Frank, please have a look ...
Comment 6 Frank Schönheit 2008-12-16 09:47:24 UTC
Couldn't reproduce with DEV300 m36 on x32 Linux. Sounds a little bit like an
x64-specific problem, in which case I'd have a hard time reproducing it, since
we don't provide Linux x64 builds.
Comment 7 drewjensen.inbox 2008-12-16 14:16:07 UTC
that's odd, the OOO_m13 and DEV300_m37 packages where both downloaded from
OpenOffice.org extended mirrors. I thought that since 3.0 64bit linux was now an
officially supported platform.
Comment 8 etfloyd 2008-12-22 16:02:11 UTC
OK, so, it only occurs on 64-bit Linux. Since 64-bit is the only Linux I use,
that tells me I'll need to continue developing this application entirely under
WinXP on a VM since that's the only 32-bit OS I have on my development machine.
It's inconvenient and it sends an unfortunate message to my client that Linux is
not really up to the task of developing or hosting serious OpenOffice-based
applications, that Win32 is the only platform we can really count on.  Is that
the message OpenOffice.org intends to send? If we're stuck with Win32 anyway,
maybe I should switch to MS Access? ;-)

Anyway, I'm not ready to give up, yet.  I looked at a number of mirrors and they
all seem to offer the 64-bit Linux package right along with the others without
any "unsupported" warnings that I could find. If 64-bit Linux platform really is
not supported here then is there some other place I can post this issue?  Who
built the 64-bit Linux package?  Is it possible that person or group would be
interested in looking into this?  Is it possible that it's a JRE/JVM issue and I
should be reporting it as a Java bug? Just looking for a little guidance...
Comment 9 drewjensen.inbox 2008-12-22 16:34:53 UTC
@etfloyd - Frank's comment about not supporting (x64) was because of my
notation. "(x64)" and not (x84_64) - I am sure - and I was just too dense at
that moment to realize what he meant.
Comment 10 oooforum (fr) 2017-04-04 16:37:29 UTC
No crash with AOO 4.1.3: closed as obsolete