Closed Bug 41831 Opened 25 years ago Closed 24 years ago

ImgDWriteReady/ImgDWrite behavior wrong

Categories

(Core :: Graphics: ImageLib, defect, P3)

Sun
Solaris
defect

Tracking

()

VERIFIED FIXED
mozilla0.9

People

(Reporter: tor, Assigned: pavlov)

References

Details

libimg doesn't seem to respect the return value from a decoders' ImgDWriteReady. Here's a trace of the calls into a decoder from a typical session (ImgDWriteReady just returning 1024 for illustration purposes): MNG::Create() MNG::MNGDecoder() MNG::ImgDInit() MNG::ImgDWrite(128) MNG::ImgDWriteReady() = 1024 MNG::ImgDWrite(2048) Assertion failed: len<MOZ_MNG_BUFSIZE-imng_p->bytesBuffered, file /cs/src/mozilla/mozilla/modules/libimg/mngcom/nsMNGDecoder.cpp, line 114 Notice that the first call to ImgDWrite occurs before libimg even checks how much data the decoder is ready to accept. After that it does get around to calling ImgDWriteReady, but ignores the response and tries dumping twice as much data into the decoder. This is causing problems with MNG integration. I can work around it for development by having a very large internal buffer, but that's wasteful and fragile.
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Blocks: mng
Keywords: nsbeta3
Target Milestone: M17 → M18
triage team: cool, but we can live without it in first release. nsbeta3-
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
Blocks: 61531
QA Contact: elig → tpreston
Blocks: 66963
Keywords: nsbeta3nsbeta1
Whiteboard: [nsbeta3-]
Target Milestone: Future → mozilla0.9
Depends on: 70938
All pnunn bugs reassigned to Pav, who is taking over the imglib.
Assignee: pnunn → pavlov
Status: ASSIGNED → NEW
code no longer used. marking fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Okay, verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.