4 replies to this topic

[Rigor O'Mortis]

Bug #1:
ADC hub, not ADC1.0-compatible...



Bug #2:
(crash report)
Code: c00000fd (Stack overflow)
Version: 1.0.0B4 (2007-08-07)
Major: 5
Minor: 1
Build: 2600
SP: 2
Type: 1
Time: 2008-01-10 14:07:52
TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI

fsma32!0x170036B7: _FSMAStopMessagePump@4
FSHTTP!0x01721631: DeletePluginObject

It's Beta 4, remains in beta 5 after update, happens every time Apex is started, "Continue appplication" makes it go away and not appear until next Apex session

Bug #2 and a half:
(this is funny, actually, not a real bug, but I thought it might make a good laugh)
Off-site image (it was too large, I use 1600x1200 screen resolution)

[Sergeo7]

Try to update/disable/uninstall F-Secure Antivirus and see if problem persist.

[Zlobomir]

@Bug 1: And you are sure that hub was ADC 1.0Final compatible?

[Rigor O'Mortis]

Zlobomir, on Jan 31 2008, 02:39 PM, said:

@Bug 1: And you are sure that hub was ADC 1.0Final compatible?

No, it WASN'T compatible, that's just the point. I understand the mainchat problem in hubs that aren't 100%-compatible, but that was just a bit weird. Downloading from a user without being able to see its name. It only identified the hub from which it comes.

Regardng bug #2 - The sollution was good. It was indeed FSecure Antivirus (although it was fully updated). Disabled it and worked.

[Zlobomir]

Rigor O'Mortis, on Jan 31 2008, 03:54 PM, said:

No, it WASN'T compatible, that's just the point. I understand the mainchat problem in hubs that aren't 100%-compatible, but that was just a bit weird. Downloading from a user without being able to see its name. It only identified the hub from which it comes.
...

Well, if the hub is not compatible, Apex can not be proved guilty... Please let us know if it happens on ADC 1.0Final compatible hubs.