Opened 11 years ago
Closed 11 years ago
#624 closed defect (notabug)
Exception: Unable to get write lock on
| Reported by: | Zoe | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Backend-Chert | Version: | 1.3.1 |
| Severity: | normal | Keywords: | fork |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
Description
Exception: Unable to get write lock on .....Couldn't fork: Cannot allocate memory
i want to read a text in a row. When it is read a certain number of rows is reported an error "Exception: Unable to get write lock on ....Couldn't fork: Cannot allocate memory"
Change History (2)
comment:1 by , 11 years ago
| Component: | Other → Backend-Chert |
|---|
comment:2 by , 11 years ago
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
No response from submitter for 4 weeks - closing as "notabug", as from the information given it sounds like you're just running out of memory.
If you have additional information, please respond and we can reopen.
Note:
See TracTickets
for help on using tickets.
This sounds like you're simply running out of memory - from the fork man page:
You can use the 'free' command to see how much memory and swap the machine has and how much is in use - if that doesn't just show you're low on memory, please paste the output here.