Opened 8 years ago

Closed 8 years ago

#736 closed defect (invalid)

arb crash

Reported by: guest Owned by: westram
Priority: blocker Milestone:
Component: ARB_NTREE Version:
Keywords: Crash Cc: niels@…

Description

Arb is installed on an Linux Mint 18 machine with 32 gb ram, as root in /usr/local/arb. It was started with the command arb /usr/local/arb/data, which has all Silva 128s .arb files. We selected the biggest one, saw there was no taxonomic tree and that there was a crash message on the console (image attached).

Attachments (2)

snapshot1.png (30.2 KB) - added by guest 8 years ago.
ARB_last_session.tgz (6.3 KB) - added by guest 8 years ago.

Download all attachments as: .zip

Change History (4)

Changed 8 years ago by guest

Changed 8 years ago by guest

comment:1 in reply to: ↑ description Changed 8 years ago by westram

  • Owner changed from devel to westram
  • Status changed from new to accepted

Replying to guest:

Arb is installed on an Linux Mint 18 machine with 32 gb ram, as root in /usr/local/arb. It was started with the command arb /usr/local/arb/data, which has all Silva 128s .arb files. We selected the biggest one, saw there was no taxonomic tree and that there was a crash message on the console (image attached).

The attached crash message is not related to arb, but anyway…

Running arb with SSURef_128_SILVA_23_09_16.arb and 32Gb of memory is quite at (or slightly over) the limit. But as you also activated 32Gb of swap-space, I'm not sure whether you really ran out of memory. To check whether that happens, you could start another console, run top there and sort processes by used memory.

From the attached log I saw you've started arb_dist. Did you try to calculate a NJ-tree or a distance matrix? Doing so would be really memory-consuming.

Please provide some additional information, what you did before the crash occurred.

comment:2 Changed 8 years ago by westram

  • Resolution set to invalid
  • Status changed from accepted to closed

Without more information I cannot investigate further or fix anything.

Note: See TracTickets for help on using tickets.