To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
User pjentsch changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from k...@openoffice.org Thu Jun 24 11:26:55 +
2010 ---
SolarMutex implementations can be found in:
vcl/os2/source/app/salinst.cxx
vcl/
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from k...@openoffice.org Thu Jun 24 11:22:08 +
2010 ---
It could, the steps are:
-1- consolidate / reduce the SalYieldMutex implementat
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Thu Jun 24 09:53:47 +
2010 ---
just for the record: the sw::UnoImplPtr that takes the SolarMutex is new in
DEV3
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from k...@openoffice.org Thu Jun 24 09:44:25 +
2010 ---
I remember, you are right. The SolarMutex is platform native implemented, ...
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Thu Jun 24 09:32:01 +
2010 ---
That would indeed be a very welcomed change.
AFAIR the implementation if SolarMu
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from k...@openoffice.org Thu Jun 24 09:09:05 +
2010 ---
Matthias, thanks for clarifying. That's what I expected.
What about doing it "
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Thu Jun 24 09:01:01 +
2010 ---
The reason for tools::SolarMutex is that you can use it without linking against
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from k...@openoffice.org Thu Jun 24 08:35:16 +
2010 ---
... somehow I have been added to this issue.
Regarding remote references to (Un
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from c...@openoffice.org Thu Jun 24 08:25:37 +
2010 ---
My own 2 cents is that I'd like to see a much longer stack to see some more
deta
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
User dtardon changed the following:
What|Old value |New value
=
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from p...@openoffice.org Wed Jun 23 11:31:05 +
2010 ---
... with the added benefit that you cannot logout or shutdown anymore because of
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Wed Jun 23 09:54:07 +
2010 ---
The user will still be able to close the application (means: all its windows) -
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from p...@openoffice.org Wed Jun 23 09:43:51 +
2010 ---
Just that looping code (aka bugs) is still possible should not prevent us from
b
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Wed Jun 23 09:25:42 +
2010 ---
> So any number of code gone wrong (hanging server, forgotten refcount) can then
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from p...@openoffice.org Wed Jun 23 09:10:15 +
2010 ---
So any number of code gone wrong (hanging server, forgotten refcount) can then
p
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Wed Jun 23 09:00:29 +
2010 ---
The SolarMutex protects all code in VCL and all other code where the developers
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from p...@openoffice.org Wed Jun 23 08:03:17 +
2010 ---
easy would not be the problem. Just that would be no solution. So you have a
Sol
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from m...@openoffice.org Wed Jun 23 07:43:32 +
2010 ---
It can't be avoided that such references exist - if they are held in a Java
prog
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
--- Additional comments from p...@openoffice.org Wed Jun 23 06:58:51 +
2010 ---
Reference or no; any call to any vcl class or even object after DeInitVCL has
be
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112605
Issue #|112605
Summary|[sw] crash during shutdown: no SolarMutex
Component|Word processor
Version|DEV300m80
21 matches
Mail list logo
