"perhaps it's necessary to build OOo with debug information first"
I don't know how to do that, but I'm willing to try with some help. The only source I could find was for the java libraries. This is a very critical problem and needs to be resolved. Too bad there isn't a developer exe release with debugging enabled. On Tue, Apr 26, 2011 at 10:36 AM, Michael Stahl <[email protected]>wrote: > On 26/04/2011 15:22, Grover Blue wrote: > > I have a muti-threaded application that processes document mostly > > asynchronous. I synchronize all UnoRuntime.* API calls, but not such > > calls as setting a table cell's value, etc. Everything runs fine in > > development, qa and in a production environment for one our clients. We > > have another client, however, where we are experience a complete > > breakdown. While processing, we continually get the following > > exception. Both clients are running version 3.3 of OpenOffice/UNO. Has > > anyone experienced this or is there a way to get more information/debug > > OpenOffice? > > you could run OOo with the debugger attached, and set a breakpoint on > thrown exceptions. but i'm not familiar with windows, and don't know > whether that would actually work on our release builds. > perhaps it's necessary to build OOo with debug information first... > > > Here is how OpenOffice is launched from bootstrapconnector: > > C:\Program Files\OpenOffice.org 3\program\soffice.exe -nologo -nodefault > > -norestore -nocrashreport -nolockcheck -headless -nofirststartwizard > > -accept=pipe,name=uno3869894507064209706;urp; > > > > Here is the RuntimeException: > > > > com.sun.star.uno.RuntimeException: [msci_uno bridge error] UNO type of > > C++ exception unknown: "std.bad_alloc", RTTI-name=".?AVbad_alloc@std@@"! > > it looks like the original exception on the C++ side is std::bad_alloc. > this exception is thrown by operator new() when a memory allocation fails. > there are also lots of places in OOo where this exception is thrown, also > after checking that some allocation failed. > > perhaps there is a leak somewhere? > does the OOo process actually use enormous amounts of RAM? > > can you see a problem by exporting the same document that fails to PDF via > the UI? > > -- > ----------------------------------------------------------------- > To unsubscribe send email to [email protected] > For additional commands send email to [email protected] > with Subject: help > -- “If the American people ever allow private banks to control the issue of their currency, first by inflation, then by deflation, the banks...will deprive the people of all property until their children wake-up homeless on the continent their fathers conquered... The issuing power should be taken from the banks and restored to the people, to whom it properly belongs." -- Thomas Jefferson "Government big enough to supply everything...is big enough to take everything you have. The course of history shows that as a government grows, liberty decreases" --- Thomas Jefferson www.CampaignForLiberty.org -- ----------------------------------------------------------------- To unsubscribe send email to [email protected] For additional commands send email to [email protected] with Subject: help
