User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:22.214.171.124pre) Gecko/20071220 Camino/1.6b1pre (like Firefox/126.96.36.199pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:188.8.131.52pre) Gecko/20071220 Camino/1.6b1pre (like Firefox/184.108.40.206pre) Saving the .jpeg in the link to disk causes an indefinite hang, forcing me to have to kill the browser. Can be reproduced if image is loaded from disk and then resaved too. This is on a Intel Macbook with OSX 10.5.1 Reproducible: Always Steps to Reproduce: 1.Load image in link 2.Save Actual Results: Camino hangs indefinitely. Expected Results: Saved the image
Can you get this to happen in Firefox 2.0.0.x too? Our image rendering code is pretty much all shared with Firefox, so it would help to know if the bug affects both browsers. It would also be useful for you to get a sample and post it here as an attachment. Instructions for getting a sample: http://caminobrowser.org/documentation/bugzilla/#hang cl
Hi. No. It isn't reproducible with Firefox 220.127.116.11. I will upload a sample when I can get activitymonitor.app (seem to have deleted it :p )... I'll attached the crash reporter stack trace / error message if that's any help (Camino was also hanging when I clicked attach here - maybe it's a problem with my system).
... 48 _FSResolveAliasFileWithMountFlagsThreadSafe + 50 (in CarbonCore) [0x96adc7d6] 48 _ResolveAliasFileWithMountFlagsCommon + 487 (in CarbonCore) [0x96ab3902] 48 _ResolveSyntheticAliasFile + 196 (in CarbonCore) [0x96ac3294] 48 __Z31ResolveSyntheticAliasFileByPathPKhmPhS1_P5FSRef + 693 (in CarbonCore) [0x96aa0205] 48 _FSPathMakeRef + 47 (in CarbonCore) [0x96a956bb] 48 __Z21FSPathMakeRefInternalPKhmmP5FSRefPh + 90 (in CarbonCore) [0x96a89b66] 43 ___open + 10 (in libSystem.B.dylib) [0x91e4be96] .. This appears to be hanging deep in filesystem code trying to bring up the save/open panel, so it sure looks like a system issue. When you do this in Firefox, does it show a save panel? I can't think of any reason the panel would be fine in Firefox and not Camino (unless perhaps it's a different default location that it's opening to).
I guess the other obvious question at this point is, does *anything* that you download by right-clicking and choosing "Download Link Target..." (which will open the panel) hang Camino?
It's been pointed out to me that we don't actually share that code with Firefox on the branch, so never mind the Firefox part of the experiment. Comment 5 would still be useful info though.
Could you reply to comment 5 please?
Whiteboard: [CLOSEME - 1/13]
Closisg based on lack of response. If you can provide the requested information, feel free to re-open this.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [CLOSEME - 1/13]
You need to log in before you can comment on or make changes to this bug.