Bug 38736 - Inserting '} ' into a cell crashes the application
Summary: Inserting '} ' into a cell crashes the application
Status: RESOLVED DUPLICATE of bug 38000
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.4.0 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-28 01:03 UTC by email
Modified: 2011-06-28 04:23 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description email 2011-06-28 01:03:46 UTC
In a spreadsheet, when you enter } and then a space into a cell, the application crashes. Entering }foo or something else without a space won't crash it, but entering a space after the } bracket will.

Happens under Windows XP 32 ger and Windows 7 x64 eng.
Comment 1 Jeffrey 2011-06-28 01:16:22 UTC
Not reproducible on LibreOffice 3.4  340m1(Build:12) on Linux. I tried typing it directly in the cell and in the formula bar, but Calc does not crash when I do so. Did you do anything else when entering "} " that might contribute to the crash?
Comment 2 email 2011-06-28 01:19:38 UTC
(In reply to comment #1)
> Not reproducible on LibreOffice 3.4  340m1(Build:12) on Linux. I tried typing
> it directly in the cell and in the formula bar, but Calc does not crash when I
> do so. Did you do anything else when entering "} " that might contribute to the
> crash?

No, I only directly opened a new Spreadsheet, and typed in "} " into the first cell, nothing else.


Forgot to set "Platform" to "Windows (All)". Didn't want to specify x86 or x86-64 though, since it happened on WinXP32 and Win7x64.
Comment 3 Rainer Bielefeld Retired 2011-06-28 04:23:45 UTC
I am pretty sure that this one is a DUP of 
"Bug 38077 - LibreOffice crashes when typing }", what itself is a DUP of
"Bug 38000 - Document crash with a closing parenthesis on the beginning of a line"

Please feel free to reopen this Bug if you find evidence that we have an independent issue here.

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