crash using invalid image location (cid:image001.jpg@01C4A618.E379E920)

RESOLVED EXPIRED

Status

()

Firefox
Shell Integration
--
critical
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Stephen Starkey, Assigned: Doron Rosenberg (IBM))

Tracking

({stackwanted})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

We had a bug in our web-based application (which we have since fixed) which
revealed an interesting behavior of Firefox when images show up with this syntax:

cid:xxxxxx

The external application window pops up trying to launch an app for "cid" and,
regardless of what we select (find or cancel), Firefox crashes.  Hard.

Reproducible: Sometimes
Steps to Reproduce:
1. Create a file with <img src="cid:something"/> somewhere in the file
2. Navigate to it in Firefox
3. Select something
4. Watch it crash (sometimes requires visiting the page multiple times)

Actual Results:  
Crash

Expected Results:  
Nothing/ignored the tag

Comment 1

14 years ago
can you please post a talkback incident id and attach a testcase? and explain
why you think this has anything to do with the plugin finder.
Keywords: stackwanted
(Reporter)

Comment 2

14 years ago
Sorry.. had it miscategorized.  This was trying to launch an external
application. Trying to reproduce again to get a Talkback incident ID (don't know
how to retrieve existing ones).
Component: Plugin Finder Service → OS Integration

Comment 3

14 years ago
there should be a talkback.exe in the components directory, you can run it at
any time.
(Reporter)

Comment 4

14 years ago
Cool.  Then, the most recent talkback incident ID is:

TB1291091Q
(Reporter)

Comment 5

14 years ago
Created attachment 162021 [details]
Sample test file

This file is of course never meant to be used in a regular web browser, but it
showed up on an internal web site before we had it corrected.

Comment 6

14 years ago
FastFind
Talkback Incident ID
	
Talkback Reports
Mozilla Reports Mozilla     Firefox Reports Firefox     Thunderbird Reports
Thunderbird     Camino Reports Camino
QuickSearch
Search By: Stack Signature Comments URL
Customize your search:
Vendor: Product: Platform: Build:
Start Date: 				End Date: 		
	(mm/dd/yyyy) 	(hh:mm:ss) 			(mm/dd/yyyy) 	(hh:mm:ss) 	
Incident ID: 1291091
Stack Signature	BackstopBrowser.exe + 0x2dcbf3 (0x006dcbf3) 9d2c7c9f
Product ID	Firefox10
Build ID	2004091322
Trigger Time	2004-10-13 15:40:59.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	BackstopBrowser.exe + (002dcbf3)
URL visited	
User Comments	
Since Last Crash	50795 sec
Total Uptime	544399 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
BackstopBrowser.exe + 0x2dcbf3 (0x006dcbf3)
BackstopBrowser.exe + 0x2832fd (0x006832fd)
BackstopBrowser.exe + 0x27298a (0x0067298a)
BackstopBrowser.exe + 0x272859 (0x00672859)
BackstopBrowser.exe + 0x18a22f (0x0058a22f)
BackstopBrowser.exe + 0x22e009 (0x0062e009)
BackstopBrowser.exe + 0x23464f (0x0063464f)
BackstopBrowser.exe + 0x184802 (0x00584802)
BackstopBrowser.exe + 0x1e13c7 (0x005e13c7)
BackstopBrowser.exe + 0x1dde32 (0x005dde32)
BackstopBrowser.exe + 0x1ddb77 (0x005ddb77)
BackstopBrowser.exe + 0x1dd50b (0x005dd50b)
BackstopBrowser.exe + 0x1de64c (0x005de64c)
BackstopBrowser.exe + 0x1e1a86 (0x005e1a86)
BackstopBrowser.exe + 0x109e22 (0x00509e22)
BackstopBrowser.exe + 0x10bfb0 (0x0050bfb0)
BackstopBrowser.exe + 0x10a382 (0x0050a382)
USER32.dll + 0x8709 (0x77d48709)
USER32.dll + 0x87eb (0x77d487eb)
USER32.dll + 0xb368 (0x77d4b368)
USER32.dll + 0xb3b4 (0x77d4b3b4)
ntdll.dll + 0xeae3 (0x7c90eae3)
USER32.dll + 0x89e8 (0x77d489e8)
BackstopBrowser.exe + 0x111c7c (0x00511c7c)
BackstopBrowser.exe + 0x3887ee (0x007887ee)
BackstopBrowser.exe + 0x1012 (0x00401012)
kernel32.dll + 0x16d4f (0x7c816d4f)

I hate to ask, but what is BackstopBrowser?
This sounds very much the same as bug 241300.
(Reporter)

Comment 8

14 years ago
Haha.. we just renamed the executable so customers don't get confused.. it's a
re-branded version of Firefox

Comment 9

14 years ago
unfortunately that confuses talkback, please rename it back before crashing :)

Comment 10

14 years ago
Can you please retest with a nightly branch build?
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.9/
(Reporter)

Comment 11

14 years ago
No crash on nightly build that I can find.  Since this was intermittent, I can't
call it conclusive.  It still pops up the little dialog, and also every so often
goes into an infinite loop (that I can break out of easily by pressing 'stop' or
browsing somewhere else) when I try refreshing the test page, but I would call
this less than critical since it is indeed intermittent.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.