461562 - Crash when closing the tab while uploading with the *new* Mediafire uploader. [@ dataRead - __memcpy]

Status: VERIFIED WORKSFORME

(Camino Graveyard :: General, defect)

Description

[Robby]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.18pre) Gecko/20081024 Camino/1.6.5pre (like Firefox/2.0.0.18pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.18pre) Gecko/20081024 Camino/1.6.5pre (like Firefox/2.0.0.18pre)

ardissone asked me to file this crash.
More details in the "Steps to Reproduce".

Reproducible: Always

Steps to Reproduce:
1. Login to Mediafire.
2. Start an upload using the new uploader which allows you to select several files to upload at once (to crash Camino, one is enough here, though).
3. Close the tab.
4. Watch Camino crash.

Comment 1

[Robby]

Attachment: Crashlog

I originally ran into this crash with a version of Camino 1.6.4 optimised for G4 Macs (unofficial).

Comment 2

[Robby]

Attachment: Full crashlog

smorgan was missing the rest of the log.

Comment 3

[Robby]

Reproduced without Input Managers.

Comment 4

[Stuart Morgan]

If they are implementing upload via CFNetwork, then it's totally divorced from our networking system, in which case I'm not sure how this would be due to anything in our code.

Comment 5

[timeless]

sounds like they should talk to apple...

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Why is Flash not showing up in any of the threads at all?  It's a Flash uploader and presumably it's Flash making the CFNetwork calls?

Comment 7

[Stuart Morgan]

It's crashing inside a callback, so if I were to guess I'd say the flow is probably:
1) Their uploader sets up a network request with some part of itself handling the callback
2) They are deallocated when the tab closes, but they don't shut down their in-flight network request.
3) The OS networking code therefore tries to call back to an object that no longer exists.

Does this happen in Camino 2.0 alpha 1? Firefox 3?

Comment 8

[Robby]

Seems fine with 2.0a1. :)

Comment 9

[Stuart Morgan]

In that case, closing WFM.