Closed
Bug 64410
Opened 24 years ago
Closed 24 years ago
Closing a new window before the image is completely rendered causes a crash
Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
People
(Reporter: chrispetersen, Assigned: pnunn)
Details
(Keywords: crash)
Attachments
(2 files)
Build: 2001010408
Platform: All
Expected result: Window should close and not crash the application.
What I got: Application crashes.
Steps to reproduce:
1) Save and open attached file.
2) Click on the second link in document.
3) This will open a new window (via target) and start to rendered a image.
4) As the image is drawing on screen, close the window. This should result in
the crash.
5) From my testing, the A element must use a target attribute to open a new
window. If the link is opened manually, like "open link in new window" via the
pop-up menu, the crash will not occur when closing it.
Reporter | ||
Comment 1•24 years ago
|
||
Reporter | ||
Comment 2•24 years ago
|
||
I can't get talkback to work after the crash on either Mac or Windows.
Reporter | ||
Comment 3•24 years ago
|
||
Reporter | ||
Comment 4•24 years ago
|
||
Peter L sent me a stack trace that he got:
FrameManager::HandlePLEvent(CantRenderReplacedElementEvent * 0x0498ece8) line
899 + 19 bytes
PL_HandleEvent(PLEvent * 0x0498ece8) line 576 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x00b88e30) line 509 + 9 bytes
_md_EventReceiverProc(HWND__ * 0x001a063c, unsigned int 49472, unsigned int 0,
long 12095024) line 1054 + 9 bytes
USER32! 77e148dc()
USER32! 77e14aa7()
USER32! 77e14bf7()
nsAppShell::Run(nsAppShell * const 0x00ba76c0) line 104 + 9 bytes
nsAppShellService::Run(nsAppShellService * const 0x00ba6750) line 408
main1(int 1, char * * 0x004a8830, nsISupports * 0x00000000) line 1019 + 32 bytes
main(int 1, char * * 0x004a8830) line 1287 + 37 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 77e992a6()
Comment 6•24 years ago
|
||
*** This bug has been marked as a duplicate of 62643 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•