Ticket #58 (reopened defect)

Opened 20 months ago

Last modified 2 weeks ago

System hangs when serially opening multiple files for viewing from an archive

Reported by: gyoung Owned by: stevenhl
Priority: minor Milestone: Release_3.14
Component: fm/2 base Version:
Keywords: hang Cc:

Description

Steven

I now am seeing a slightly different hang using the beta 6. It seems to happen when I serially open several files from an archive I am viewing. For example I open the ACPI archive then view the ACPI.doc close it then view ACPISMP.doc close it then try to view any other of the doc files the archive (unzip) window opens and will hang with the window title reading closing unzip. I can't get to CADPOP but if I hit CAD multiple times the machine reboots. Just before the reboot WPS & FM2 unfreeze and start to complete the operation. Unfortunately, this is very intermittent and I haven't been able to create a test case. There is no popup log entry. Thanks

Gregg

I saw this again this morning only this time it occurred when I opened an archive containing one small file. It opened but the system immediately became non responsive. Same result as above. The archive file work fine after the reboot.

I have also noticed that it occurs while I am scrolling with a wheel mouse using the amouse driver. I remember that at one point I was able to scroll off the end of the internal viewer because of the specific call that amouse makes for scrolling. Is it possible this hang is related. Again this is not reproducible but occurs occasionally.

Gregg

Change History

Changed 20 months ago by gyoung

The second part above seems to have been fixed by changing dossleep(0) to dossleep(1) in the threads.

The hang has occurred both with hyperview (resident in memory mode) and FTE.

Changed 19 months ago by stevenhl

  • keywords hang added
  • owner changed from StevenHL to stevenhl
  • status changed from new to assigned
  • milestone set to Release_3.05_beta8

Changed 18 months ago by gyoung

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

Changed 18 months ago by gyoung

  • status changed from closed to reopened
  • resolution deleted

Changed 18 months ago by stevenhl

  • owner changed from stevenhl to gyoung
  • status changed from reopened to new

Changed 18 months ago by stevenhl

  • owner changed from gyoung to stevenhl,gyoung

Changed 18 months ago by stevenhl

  • owner changed from stevenhl,gyoung to stevenhl
  • status changed from new to assigned

Changed 18 months ago by gyoung

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

Changed 12 months ago by gyoung

  • status changed from closed to reopened
  • resolution deleted

This reoccurred when the DosSleep? was reduced to 50 from 100. I have increased it back as a temporary fix. The race condition should be identified and addressed directly with a flag or semaphore.

Changed 12 months ago by gyoung

  • priority changed from critical to minor
  • milestone changed from Release_3.5.8 to Release_3.8

Changed 10 months ago by gyoung

  • milestone changed from Release_3.8 to Release_3.9

Changed 8 months ago by gyoung

  • milestone changed from Release_3.9 to Release_3.10

Changed 7 weeks ago by gyoung

  • status changed from reopened to closed
  • resolution set to worksforme

Changed 7 weeks ago by gyoung

  • status changed from closed to reopened
  • resolution deleted

Changed 7 weeks ago by stevenhl

  • milestone changed from Release_3.12 to Release_3.13

Changed 2 weeks ago by gyoung

Something is haning in the exit list in all likelihood.

Note: See TracTickets for help on using tickets.