Delicious Bookmark on Delicious

Ticket #6 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Client running project not in database crashes FahMon

Reported by: uncle_fungus Assigned to: uncle_fungus
Priority: blocker Milestone: 2.3.1
Component: Monitoring system Keywords:
Cc:

Description

The attached FAHLog will crash FahMon on Windows (RU)

Attachments

FAHlog.txt (15.9 kB) - added by uncle_fungus on 10/16/07 10:44:52.
SMP FAHlog

Change History

10/16/07 10:44:52 changed by uncle_fungus

  • attachment FAHlog.txt added.

SMP FAHlog

10/16/07 10:45:19 changed by uncle_fungus

  • status changed from new to assigned.

(in reply to: ↑ description ) 10/16/07 11:02:15 changed by uncle_fungus

Replying to uncle_fungus:

The attached FAHLog will crash FahMon on Windows (RU)

The same log appears to work fine in both Linux and the OS X conversion

(in reply to: ↑ description ; follow-up: ↓ 6 ) 10/22/07 17:24:08 changed by uncle_fungus

  • status changed from assigned to closed.
  • resolution set to worksforme.

Replying to uncle_fungus:

The attached FAHLog will crash FahMon on Windows (RU)

I'm going to close this as "Works for me"

It may be re-opened if the behaviour is observed again.

10/25/07 06:27:39 changed by uncle_fungus

  • milestone set to 2.3.1.

10/27/07 05:14:15 changed by uncle_fungus

  • status changed from closed to reopened.
  • resolution deleted.

(in reply to: ↑ 3 ; follow-up: ↓ 10 ) 10/27/07 05:16:13 changed by uncle_fungus

Replying to uncle_fungus:

Replying to uncle_fungus:

The attached FAHLog will crash FahMon on Windows (RU)

I'm going to close this as "Works for me" It may be re-opened if the behaviour is observed again.

Discovered the situation that causes this bug. If a new project is encountered that isn't in the project database, FahMon will crash. This will be somewhere in the new progress checking code, which seems to be missing some sanity checking

10/27/07 05:16:36 changed by uncle_fungus

  • status changed from reopened to new.

10/27/07 05:16:43 changed by uncle_fungus

  • status changed from new to assigned.

10/27/07 11:18:30 changed by uncle_fungus

  • summary changed from SMP client crashes FahMon to Client running project not in database crashes FahMon.

(in reply to: ↑ 6 ) 10/28/07 08:00:29 changed by uncle_fungus

  • status changed from assigned to closed.
  • resolution set to fixed.

Replying to uncle_fungus:

Replying to uncle_fungus:

Replying to uncle_fungus:

The attached FAHLog will crash FahMon on Windows (RU)

I'm going to close this as "Works for me" It may be re-opened if the behaviour is observed again.

Discovered the situation that causes this bug. If a new project is encountered that isn't in the project database, FahMon will crash. This will be somewhere in the new progress checking code, which seems to be missing some sanity checking

Fixed in r92