If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

window.open() does not complete with cache turned off

RESOLVED WORKSFORME

Status

()

Core
Networking: Cache
RESOLVED WORKSFORME
17 years ago
16 years ago

People

(Reporter: Alexandru Savulov, Assigned: John Taylor)

Tracking

({hang})

Trunk
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
turning the cache(s) off (memory and disk = 0) will cause javascript calls like

 window.open("http://www.google.com");

hang (or never complete) and after closing all the process's windows the process 
will not terminate and remain running in the background. subsequent tries to 
start mozilla fail.
(Reporter)

Comment 1

17 years ago
Created attachment 38000 [details]
reduced test case
(Reporter)

Comment 2

17 years ago
added "hang" - thuogh its just a hang at the end (process does not exit)
Keywords: hang
(Reporter)

Comment 3

17 years ago
changed the component (don't really think that is a cache bug - my mistake)
Assignee: gordon → rogerl
Component: Networking: Cache → Javascript Engine
QA Contact: tever → pschwartau

Comment 4

17 years ago
Here is the HTML behind the testcase:

<html>
<head>
<script language="JavaScript">

<!--
function preload()
{
 window.open("http://www.google.com");
}
-->

</script>
 
</head>
<body>
Turn both caches off (set memory and disk cache = 0) then 

      <A href="javascript:preload()">click here</a>

 ...<br><br>NOTE:<br>
After you closed all the windows you'll have to kill the process too!

</body>
</html>

Comment 5

17 years ago
Confirming bug with trunk build 20010607xx WinNT. As instructed, I set
my disk and memory cache to 0, closed Mozilla, and repopened it.

The first time I tried the testcase, I did not have any problem.
The window.open correctly brought up a new window; I closed it; 
and then I closed the main window; there were no stray mozilla.exe
processes; I was able to bring up Mozilla again with no problem

However, the SECOND time I tried the testcase, the window.open
FAILED to bring up a new window. Then, when I closed the main window,
there was a stray, unseen mozilla.exe process that had to be killed
before you could bring up Mozilla again - exactly as described above.

Browser, not engine. Reassigning to Embedding:Docshell for further triage.
I'm not sure this is the correct component...but definitely not JavaScript 
Engine.
Assignee: rogerl → adamlock
Component: Javascript Engine → Embedding: Docshell
QA Contact: pschwartau → adamlock
Summary: javascript calls does not complete with cache turned off → window.open() does not complete with cache turned off

Comment 6

17 years ago
If I set mem and disk cache to 0, quit and restart Mozilla I don't even get a
navigator window. It just hangs somewhere after webshell count goes up to 2.
Breaking into the code at this point gives no clues.

I would hazard that it is a problem with chrome: or file: protocol when cache is
disabled. Reassigning to netwerk cache for ideas.
Assignee: adamlock → gordon
Component: Embedding: Docshell → Networking: Cache
QA Contact: adamlock → tever

Comment 7

16 years ago
John, can you take a look at this?  This is a similar one.
Assignee: gordon → jtaylor
(Assignee)

Comment 8

16 years ago
Marking WORKSFORME. adam and alexsavulov: are you still seeing this? Phil and I
can't seem to reproduce.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 9

16 years ago
not seeing this anymore. (0.9.2 branch pull 7.9.01)
You need to log in before you can comment on or make changes to this bug.