This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 78514 - Installer failing to start without proper error message if there is not enough temp space
Summary: Installer failing to start without proper error message if there is not enoug...
Status: RESOLVED WONTFIX
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Kirill Sorokin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-20 11:56 UTC by mariadavydova
Modified: 2006-06-21 01:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
install failure (19.64 KB, application/octet-stream)
2006-06-20 11:59 UTC, mariadavydova 		Details
install failure (43.62 KB, application/octet-stream)
2006-06-20 12:00 UTC, mariadavydova 		Details
install failure (42.49 KB, application/octet-stream)
2006-06-20 12:00 UTC, mariadavydova 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mariadavydova 2006-06-20 11:56:30 UTC 
tpr1 rc1 build:
This is reported by Manish Malhotra:
Install failures w/ RC1 that I experienced... cause seems to be low disk space
when failure happened
(less than 300MB).

Having about 400MB seems to be OK yet performance was poor (that may
be a disk paging issue given #processes active on my system at the time)... 

See attachments for snapshots.
Comment 1 mariadavydova 2006-06-20 11:59:15 UTC 
Created attachment 31210 [details]
install failure
Comment 2 mariadavydova 2006-06-20 12:00:05 UTC 
Created attachment 31211 [details]
install failure
Comment 3 mariadavydova 2006-06-20 12:00:27 UTC 
Created attachment 31212 [details]
install failure
Comment 4 Kirill Sorokin 2006-06-21 01:08:32 UTC 
The root cause for this issue is an InstallShield engine bug. It was accepted by
their support folks, but no esitmates are given on when (or whether) it will be
fixed. Resolving as WONTFIX, since there is nothing we can do about it.