Task #10245 (new)
Opened 11 years ago
Last modified 8 years ago
BUG: Resource issues with OMERO.tables — at Version 1
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | analysis@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by spli)
I've been seeing some strange behaviour with OMERO.tables when making a large number of calls to add data from OMERO.scripts. This includes scripts exiting due to a failure to communicate with the Tables service, the Tables service using 100% CPU even after all clients have disconnected, apparent out-of-memory errors with theTables service (manifested as an OS X "Problem Report for Python" dialog).
Further investigation suggets this is due to opening/closing a table too frequently. For instance, reusing a connection/handle to a table instead of opening and closing the table for every operation (read, addData) seems to work fine. Still a bug though.
Change History (2)
Changed 11 years ago by spli
comment:1 Changed 11 years ago by spli
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
