Bug Hunting Session
Bug 55560 - EDITING: CRASH when Format Cells (menu and Context menu)
Summary: EDITING: CRASH when Format Cells (menu and Context menu)
Status: RESOLVED DUPLICATE of bug 55685
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.0.0.0.alpha0+ Master
Hardware: x86 (IA32) Windows (All)
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks: mab4.0
  Show dependency treegraph
 
Reported: 2012-10-03 04:52 UTC by Korrawit Pruegsanusak
Modified: 2012-10-12 09:41 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
WinDbg log with backtrace (22.45 KB, text/plain)
2012-10-10 12:19 UTC, Korrawit Pruegsanusak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Korrawit Pruegsanusak 2012-10-03 04:52:59 UTC
On Windows XP
- Open new Spreadsheet
- Right-click any cell
- Select "Format Cells..."
- CRASH

Might be related to bug 54861, but that bug is in 3.5 branch. This is recent master regression bug.

REPRODUCIBLE with
* build from W2008R2@20-With-Symbol-Bytemark-Hosting, pull time 2012-09-29 05:32:03, core: 4671e25d99bb2ad0f4f8f68c25fcc1bfce9e79b8

* build from W2008R2@20-With-Symbol-Bytemark-Hosting, pull time 2012-10-01 05:02:30, core: e12f501bebf83ea8121e517283c25c24587268a7

NOT REPRODUCIBLE with
* build from W2008R2@16-minimal_build, pull time 2012-09-28 00:02:27, core: 77a0acae58828d2186bce241b562c363da93343b
Comment 1 Rainer Bielefeld Retired 2012-10-08 11:25:08 UTC
Still [Reproducible] blank new document and with Server-installation of Master "3.7.0.alpha0+  – ENGLISH UI [Build ID: f2e622]" {tinderbox: Win-x86@16, pull time 2012-10-06 09:31:39} on German WIN7 Home Premium (64bit) UserInstallation=$SYSUSERCONFIG/LOdev/3

CRASH also appears for menu 'Format -> Cells'

@Spreadsheet Team
Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf (and remove others in team from CC).
Comment 2 Eike Rathke 2012-10-08 12:20:17 UTC
Could not reproduce on Linux with a current (as of 2012-10-04) master unxlngx6 dbgutil build.
Comment 3 Julien Nabet 2012-10-08 19:19:14 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce either the problem.
Comment 4 Julien Nabet 2012-10-08 19:53:23 UTC
bfo: if you reproduce this on Windows, could you retrieve a bt?
I wonder if it could be a dup of fdo#55685
thank you in advance.
Comment 5 Julien Nabet 2012-10-08 20:30:40 UTC
bfo: sorry, this one is about Calc, the other about Writer. So don't think it's a dup. Of course, bt is still useful :-)
Comment 6 bfoman (inactive) 2012-10-08 21:00:56 UTC
Confirmed with:
LO 3.7.0.0.alpha0+ 
Build ID: e12f501
Pull time: 2012-10-01 05:02:30
Windows XP Professional SP3

Unfortunately I do not have my own 3.7 debug build with symbols and sources ATM.
Bt as in bug 55685 can be produced by anyone with Debugging tools for Windows and latest zippped daily from W2008R2@20-With-Symbol-Bytemark-Hosting installed.
Comment 7 Markus Mohrhard 2012-10-09 05:53:23 UTC
(In reply to comment #2)
> Could not reproduce on Linux with a current (as of 2012-10-04) master
> unxlngx6 dbgutil build.

And memcheck does not show any problem.
Comment 8 Roman Eisele 2012-10-09 07:13:03 UTC
(In reply to comment #5)
> bfo: sorry, this one is about Calc, the other about Writer. So don't think
> it's a dup.

Not a dup, of course, but nevertheless the bugs could be closely related, because all these dialog windows (“Character”, “Paragraph”, “Cell”) share much code, don’t they?

(I learned from some other bugs that if under certain circumstances Calc: “Format > Cell > Border” crashes, under the same circumstances will also crash Writer: “Format > Paragraph > Border”, and the same is true at least for the background and highlight color settings.)

*

PS: Just like bug 55685, this one is NOT reproducible on Mac OS X 10.6.8 (with master build dated 2012-10-04), so really Windows only.
Comment 9 Korrawit Pruegsanusak 2012-10-10 12:19:56 UTC
Created attachment 68401 [details]
WinDbg log with backtrace

With my own build on Windows 7 x64, master at 7b34748b1bfd8b5fe0406c1f6bdaaa585d7bc4c3 (Oct 9, 2012), --enable-symbols, --enable-epm, --with-package-format=installed, I can reproduce the problem. Attached is WinDbg log with backtrace.
Comment 10 Korrawit Pruegsanusak 2012-10-10 12:25:40 UTC
Hello Caolan,

After I've done WinDbg for bug 55685, I think it is a duplicate, because they have same points of FAULTING_SOURCE_CODE, and share 6 top of stack trace.

So, could you please have a look here? Thanks :-)
Comment 11 Caolán McNamara 2012-10-12 09:41:51 UTC

*** This bug has been marked as a duplicate of bug 55685 ***