To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=101280
------- Additional comments from [email protected] Wed Jul 1 09:13:46 +0000 2009 ------- I have no intention to hijack this bug. "Stop" should return to user control. When your PC has been churning 5 hours on a 400 MB table I guess you run out of physical memory and start swapping. Even if OOO sends an SQLCancel to the driver while doing the select * from table, which I couldn't verify, and the driver does cancel the operation correctly, I would expect that cleaning up the resultset in the driver and OOO would take also a lot of time because of swapping and cause a long delay to regain user control. Shouldn't take hours though. Could you check memory usage before and after stop? After you push stop, is OOO consuming CPU or is it idling? Some ODBC drivers are reported to have problems with SQLCancel not doing anything.(mysql 3.51, oracle 9.2.0.7.0 with oracle server on NT, DB2 client 7.?, ...). This would also cause ooo to hang around not releasing user control. What driver are you using? Issue 66846 reports OOO crashing on out of memory conditions opening large tables. JDBC apparently reports an out of heap memory condition. Not sure what your odbc driver is doing: stop and report or just sit there. If getting 1MB of data out of a 400MB database isn't possible because of "just the wrong way about things", I for sure call that a bug. Even a show stopper. I'm considering raising priority on issue 102625.... --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
