[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=45303

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |INSUFFICIENTDATA

--- Comment #10 from QA Administrators  ---
Dear Bug Submitter,

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-20170301

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=45303

--- Comment #9 from QA Administrators  ---
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping-20170131

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=45303

Julien Nabet  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #8 from Julien Nabet  ---
Let's put this one to NEEDINFO meanwhile.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=45303

Kevin Suo  changed:

   What|Removed |Added

 CC||suokunl...@126.com

--- Comment #7 from Kevin Suo  ---
Any update on this 4-years-old bug? Is the bug still exist in the recent
versions?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=45303

--- Comment #6 from QA Administrators qa-ad...@libreoffice.org ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

   Test to see if the bug is still present on a currently supported version of
LibreOffice (4.4.3 or later)
   https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of
LibreOffice and your operating system, and any changes you see in the bug
behavior

 If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a short comment that includes your version of
LibreOffice and Operating System

Please DO NOT

   Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so: 1. Download and install oldest version of LibreOffice
(usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 
3. Leave a comment with your results;
4a. If the bug was present with 3.3 - set version to inherited from OOo; 
4b. If the bug was not present in 3.3 - add regression to keyword


Feel free to come ask questions or to say hello in our QA chat:
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-06-08

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=45303

Julien Nabet serval2...@yahoo.fr changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #5 from Julien Nabet serval2...@yahoo.fr ---
Any update with more recent LO version? (knowing that we use now Python 3.X)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=45303

Stephan Bergmann sberg...@redhat.com changed:

   What|Removed |Added

 CC||sberg...@redhat.com

--- Comment #4 from Stephan Bergmann sberg...@redhat.com 2012-01-31 07:06:33 
PST ---
FWIW, just had a related-looking abort (--enable-dbgutil glibc double free or
corruption (fasttop)) from within pyuno::GCThread during sw_complex test;
appears to only happen sporadically, as subsequent runs of sw_complex succeeded
again.


Core was generated by
`/data/lo/core/solver/unxlngx6/installation/opt/program/soffice.bin
-env:UserIns'.
Program terminated with signal 6, Aborted.
#0  0x0037e6836285 in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);

Thread 5 (Thread 0x7f792affd700 (LWP 15902)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x7f794ec2add9 in osl_waitCondition (Condition=0x7f792020f0d0,
pTimeout=0x7f792affca50) at /data/lo/core/sal/osl/unx/conditn.cxx:264
#2  0x7f794dc3470a in cppu_threadpool::ThreadPool::waitInPool
(this=0x7f7930004660, pThread=0x7f791c000db0) at
/data/lo/core/cppu/source/threadpool/threadpool.cxx:197
#3  0x7f794dc3105a in cppu_threadpool::ORequestThread::run
(this=0x7f791c000db0) at /data/lo/core/cppu/source/threadpool/thread.cxx:240
#4  0x7f794dc30740 in cppu_requestThreadWorker (pVoid=0x7f791c000db0) at
/data/lo/core/cppu/source/threadpool/thread.cxx:57
#5  0x7f794ebe53c3 in osl_thread_start_Impl (pData=0x7f791c001040) at
/data/lo/core/sal/osl/unx/thread.c:292
#6  0x0037e6c07d90 in start_thread (arg=0x7f792affd700) at
pthread_create.c:309
#7  0x0037e68ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 4 (Thread 0x7f790700 (LWP 15913)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x7f794ec2add9 in osl_waitCondition (Condition=0x7f79080333d0,
pTimeout=0x7f790fffea50) at /data/lo/core/sal/osl/unx/conditn.cxx:264
#2  0x7f794dc3470a in cppu_threadpool::ThreadPool::waitInPool
(this=0x7f7930004660, pThread=0x7f791c0028b0) at
/data/lo/core/cppu/source/threadpool/threadpool.cxx:197
#3  0x7f794dc3105a in cppu_threadpool::ORequestThread::run
(this=0x7f791c0028b0) at /data/lo/core/cppu/source/threadpool/thread.cxx:240
#4  0x7f794dc30740 in cppu_requestThreadWorker (pVoid=0x7f791c0028b0) at
/data/lo/core/cppu/source/threadpool/thread.cxx:57
#5  0x7f794ebe53c3 in osl_thread_start_Impl (pData=0x7f791c002910) at
/data/lo/core/sal/osl/unx/thread.c:292
#6  0x0037e6c07d90 in start_thread (arg=0x7f790700) at
pthread_create.c:309
#7  0x0037e68ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x7f79457b3700 (LWP 15894)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x7f794ebfa7ae in rtl_cache_wsupdate_wait (seconds=10) at
/data/lo/core/sal/rtl/source/alloc_cache.cxx:1411
#2  0x7f794ebfa985 in rtl_cache_wsupdate_all (arg=0xa) at
/data/lo/core/sal/rtl/source/alloc_cache.cxx:1551
#3  0x0037e6c07d90 in start_thread (arg=0x7f79457b3700) at
pthread_create.c:309
#4  0x0037e68ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f79457c58c0 (LWP 15893)):
#0  0x0037e687c69a in malloc_consolidate (av=0x7f792020) at
malloc.c:4264
#1  0x0037e687d3c9 in malloc_consolidate (av=0x7f792020) at
malloc.c:4227
#2  _int_free (av=0x7f792020, p=optimized out, have_lock=0) at
malloc.c:4158
#3  0x7f794ac1c7fe in
__gnu_cxx::new_allocatorutl::FontNameAttr::deallocate (this=0x7f792007d950,
__p=0x7f792007da00) at
/usr/lib/gcc/x86_64-redhat-linux/4.6.2/../../../../include/c++/4.6.2/ext/new_allocator.h:98
#4  0x7f794ac19030 in std::__cxx1998::_Vector_baseutl::FontNameAttr,
std::allocatorutl::FontNameAttr ::_M_deallocate (this=0x7f792007d950,
__p=0x7f792007da00, __n=352) at
/usr/lib/gcc/x86_64-redhat-linux/4.6.2/../../../../include/c++/4.6.2/bits/stl_vector.h:156
#5  0x7f794ac180b2 in std::__cxx1998::_Vector_baseutl::FontNameAttr,
std::allocatorutl::FontNameAttr ::~_Vector_base (this=0x7f792007d950,
__in_chrg=optimized out) at
/usr/lib/gcc/x86_64-redhat-linux/4.6.2/../../../../include/c++/4.6.2/bits/stl_vector.h:142
#6  0x7f794ac1596c in std::__cxx1998::vectorutl::FontNameAttr,
std::allocatorutl::FontNameAttr ::~vector (this=0x7f792007d950,
__in_chrg=optimized out) at
/usr/lib/gcc/x86_64-redhat-linux/4.6.2/../../../../include/c++/4.6.2/bits/stl_vector.h:351
#7  0x7f794ac1446d in std::__debug::vectorutl::FontNameAttr,
std::allocatorutl::FontNameAttr ::~vector (this=0x7f792007d950,
__in_chrg=optimized out) at

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=45303

--- Comment #3 from Yifan Jiang yfji...@novell.com 2012-01-30 01:30:06 PST ---
(In reply to comment #2)
 I saw this log in the master build around 6th/Jan as well.

As a complementary, in my master build the Invalid read of size 4 errors were
logged, but soffice.bin still survived without crash.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=45303

Yifan Jiang yfji...@novell.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1

--- Comment #2 from Yifan Jiang yfji...@novell.com 2012-01-28 22:10:52 PST ---
I saw this log in the master build around 6th/Jan as well.

But couldn't see the similar thing in 3.5 rc2 pre-release build.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 45303] python corrupting memory on print ?

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=45303

--- Comment #1 from Michael Meeks michael.me...@novell.com 2012-01-27 
04:49:42 PST ---
Created attachment 56220
  -- https://bugs.freedesktop.org/attachment.cgi?id=56220
sample document (prolly unrelated)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs