Bug 134292 - Crash in: com::sun::star::uno::Sequence<signed char>::~Sequence<signed char>()
Summary: Crash in: com::sun::star::uno::Sequence<signed char>::~Sequence<signed char>()
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-25 05:03 UTC by vijaya chandra
Modified: 2021-01-23 04:04 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["com::sun::star::uno::Sequence<signed char>::~Sequence<signed char>()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vijaya chandra 2020-06-25 05:03:25 UTC
This bug was filed from the crash reporting server and is br-63f3f9e4-6b67-468e-ba83-d1e20e325a71.
=========================================
Comment 1 Julien Nabet 2020-06-25 07:16:22 UTC
Could you follow https://wiki.documentfoundation.org/QA/FirstSteps and if you still reproduce this, could you indicate minimum step by step process to reproduce this?
Comment 2 QA Administrators 2020-12-23 03:45:21 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-01-23 04:04:09 UTC
Dear vijaya chandra,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp