Closed
Bug 2256
Opened 26 years ago
Closed 26 years ago
[PP] Large images appear as empty frame (needs huge RAM partition)
Categories
(Core Graveyard :: Viewer App, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
M4
People
(Reporter: elig, Assigned: pnunn)
Details
* TITLE/SUMMARY
[PP] Large image files only appear as empty frame (needs mondo-huge RAM
partition)
* STEPS TO REPRODUCE
0) Launch Viewer
1) View these images:
a. http://www.jpl.nasa.gov/files/images/hi-res/p46411.jpg (328K)
b. http://www.jpl.nasa.gov/files/images/hi-res/p43883.gif (1.6M)
c. http://www.jpl.nasa.gov/files/images/hi-res/p43886.jpg (4.8M)
* RESULT
- What happened
With a 10 MB RAM partition, viewer won't display image a. (Works with a 20 MB
partition.)
With a 20 MB partition, neither image b nor c will display.
- What was expected
Large image files should be displayed on Mac using a reasonable memory partition.
This is more than likely, at its core, a duplicate of 2255 ("[PP] Large-
dimensioned PNG files crash Mac viewer"), which is also memory-required.
However, since the application behavior is very different here (no crash, just an
empty image frame), I'm writing it up separately.
* REGRESSION
- Occurs On
viewer (1.8.98 build for Mac OS, 20 MB RAM Partition, VM enabled)
- Doesn't Occur On
viewer (1.7.98 build for Win32)
viewer (1.8.98 build for Linux)
* CONFIGURATIONS TESTED
- PowerMac 8500/120 (233 Mhz 604e), 64 MB RAM, 1024x768 (16-bit video), Mac OS
8.5.1
I don't think this is imglib related. Maybe Mac cache problem or
netlib cache problem. I'll accept it, study it more & pass it on if
necessary.
-pn
Comment 2•26 years ago
|
||
I found a bug in the mac allocators that would cause them to fail for single
memory allocations over 1MB in size. This would not explain why it works
sometimes, though. I'll be checking in a fix tomorrow.
Reporter | ||
Comment 6•26 years ago
|
||
Thanks for pointing that out, Pam. Somehow missed Simon's comment; will check
today.
Reporter | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 7•26 years ago
|
||
Using 2.1.99 build, verified that S/i/m/o/n/ k/i/c/k/s/ a/s/s the bug is now
fixed.
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•