Author Topic: NANY 2011 Release: JottiQ (Read 264099 times)

skwire · « **Reply #150 on:** January 21, 2011, 08:49 AM »

Seems to be fixed here as well.

pr1m35 · « **Reply #151 on:** January 21, 2011, 09:31 AM »

The host I'm using is Windows XP SP3 (fully patched as of 01/21/2010) running as a guest on a Citrix XenServer (5.6.0) - I'm not sure if anyone else is running JottiQ on a VM but this is the only place I can safely conduct my malware analysis in my environment

Anyhow - I installed using the installer (20110106 JottiQ (1.0.2).exe) and double checked the correct .NET and C re-distributables were installed properly

My issue is, as soon as I try to open JottiQ (from Start-Menu or otherwise) it crashes and Windows wants to send a crash report to Microsoft

This is the message I get:

JottiQ has encountered a problem and needs to close. We are sorry for the inconvenience.

Here's the gist of the crash report:

EventType : clr20r3 P1 : jottiq.exe P2 : 1.0.2.22338 P3 : 4d25a674 P4 : presentationcore P5 : 4.0.0.0 P6 : 4ba1f865 P7 : 44dd P8 : 47 P9 : system.io.fileformatexception

Any ideas what could be causing this? Really hopping to use JottiQ

worstje · « **Reply #152 on:** January 21, 2011, 10:34 AM »

pr1m35, it sounds like you might suffer the same issue jCat reported a few days ago. If you look on the previous page, only a few hours ago I posted a 1.0.3 test-build that might solve the issue. Can you test that one and report whether it fixes the issue?

In the case it does not fix the issue, can you per chance check your Event log, Application tab, and paste the stack trace? Hopefully yours is going to be a bit more useful that jCat, regardless of them being the actual same thing.

mouser · « **Reply #153 on:** January 22, 2011, 07:21 PM »

written up on the ilovefreesoftware site:
http://www.ilovefree...e-virus-scanner.html

worstje · « **Reply #154 on:** January 23, 2011, 02:12 AM »

Thanks for the link.

What really excited me is the option to scan running processes.
-ILoveFreeSoftware

I have a feeling that is a common opinion, yet it is the buggiest feature there is in JottiQ to the point I'm thinking of removing it. JottiQ v1.1.0 might end up losing me a lot of users if I end up going that route.

jCat · « **Reply #155 on:** January 25, 2011, 04:33 PM »

Hi worstje,

I'm posting delayed reply ... again

As a reminder, I don't have any system messages as described by pr1m35 in Reply #151 ... All is silent here

No, unfortunately 1.0.3 test-build didn't solve a problem here. Same stack of .Net Framework Events
Well, you may compare with the previous one

[Select]

Application: JottiQ.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileFormatException
Stack:
at System.Windows.Window.ShowDialog()
at JottiQ.App.AppStartup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.runTryCode(System.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at JottiQ.App.Main()

Regards

p.s. currently I cannot read PM received from you - "due to server problem" as this site stated

worstje · « **Reply #156 on:** January 25, 2011, 04:54 PM »

Yeah I heard from p1m35 that it didn't solve the issue for him either earlier today.

Sadly, the stuff happens inside .NET, and as long as I can't reproduce it or have access to a system to try and reproduce the issue on it is very damn annoying to try and figure the bug out.

Try this build. It will either 'fix' it because I removed some code just now out of desperation, or it will throw out some (hopefully extra-nice errors) to help me try and find the problem. Or it will throw out the exact same stracktrace.

jCat · « **Reply #157 on:** January 25, 2011, 11:12 PM »

Try this build. It will either 'fix' it because I removed some code just now out of desperation, or it will throw out some (hopefully extra-nice errors) to help me try and find the problem. Or it will throw out the exact same stracktrace.
-worstje link=topic=24663.msg233759#msg233759

Very quick reply after a very brief testing of the latest 1.0.3 build 42939

Got all initial ... & further screens ... scanned 3 files queued... no .Net Errors logged

1st impression - great!

Well done! I'll try to post anything that can be find either a lil bug(s) ...hope not

or the Wish List entries if any

Best regards! Cheers!

worstje · « **Reply #158 on:** January 26, 2011, 07:09 AM »

Well, that is just a great bucket of poppycock.

I hate you, .NET framework.

Would either you or p1m35 be willing to run another testbuild? The code I removed, while not essential, is nice-to-have and present in about 5 other places where it apparently causes no crashes at all for you, and that confuses the hell outta me. I'd hate to release another version while I don't understand why this fixed it: by my logic it should still crash for you on the main screen, settings screen or the about box, and apparently it does not.

Another test build - the final one I'll ask you to test, promise.

jCat · « **Reply #159 on:** January 27, 2011, 09:55 PM »

Well, that is just a great bucket of poppycock. I hate you, .NET framework.
-worstje (January 26, 2011, 07:09 AM)

hahaha! Oh dear !

True! Don't ask. I am a programmer myself.
The idea behind .Net is fine. I do not agree with people who are saying that they are not willing to use this or that Software just because they are compelled to download xxx MB of Framework - that is just stupid!
At the same time the implementation of the thing with many versions & bugs & incompatibilities and so on & so forth - is just an insanity by the company that promotes Object Oriented Design
It seems that "Small & Soft" doesn't have enough resources or something

... digressing ...I have many stories about the Framework(s) & suffering & fixing ...

...I don't understand why this fixed it: by my logic it should still crash for you on the main screen, settings screen or the about box, and apparently it does not.
-worstje (January 26, 2011, 07:09 AM)

Cannot tell about the "About Box", since until the latest test release I could not get anything & now I am having everything

Another test build - the final one I'll ask you to test, promise.
-worstje (January 26, 2011, 07:09 AM)

The test will be downloaded & performed. There is no need to "promise the last one".
Anytime; any other build, man, as soon as I have time

Cheers!

jCat · « **Reply #160 on:** January 28, 2011, 03:17 PM »

adding to the above post

Attached is a combined output of 2 debug messages that you asked for
Other than that the Application is running fine after confirming both

Moreover, interestingly enough - after rebooting and running the App. this morning I did not receive any of those messages

Cheers!

worstje · « **Reply #161 on:** January 28, 2011, 04:48 PM »

Thank you jCat! This was exactly the information that I was looking for.

Now, rather than remove that code for all XP users, I can just run it and ignore any errors that happen, which I prefer by far over any of the other alternatives.

I have no clue why it stopped causing those messages, although my best bet is that your Windows Imaging Component got updated. It's basically a part of Windows that can read and decode tons of images - except most applications don't use it and instead use something else. (I wonder why, with all the bloody bugs that's in that thing...)

Once mouser finishes his prodding and poking with dcuhelper.exe, JottiQ v1.0.3 will be released. $:-\$

worstje · « **Reply #162 on:** January 28, 2011, 11:43 PM »

Right before January ends, a bugfix release of everyones favorite lady-bug.

Lots of thanks to jCat who helped to test all those test builds I worked up to try and find the elusive issue that was crashing JottiQ for him and pr1m35. (Any of the dcuhelper.exe updates I alluded to above will have to wait as those are going to take a while to finish up and they're not all that essential to have at all.)

If there is anything else you want to know, check the first post in this topic or see the website.

v1.0.3 (2011-01-29)

    JottiQ v1.0.2 still had a few weird bugs left. Hereby they shall be thought
    of as relics of the old past, of times gone by and much, much more...
    
      Added: Update check is now automatically done every few days when JottiQ
          is started. The automatic checking behaviour can be disabled in the
          Settings window.
      Fixed: Opening the 'About JottiQ' for a second time will no longer crash
          JottiQ on Windows XP. It was a weird bug, but not as weird as...
      Fixed: Starting JottiQ on some installations of Windows XP would cause an
          instant crash. This was a pain to track down, but it has now been
          utterly vanquished. Many thanks to jCat for the help in tracking down
          what was causing this nasty issue.

mouser · « **Reply #163 on:** January 30, 2011, 10:23 AM »

nice

sujay85 · « **Reply #164 on:** February 26, 2011, 09:56 AM »

I would like to request a feature in JottiQ. Please add internet connection through proxy with authentication.

worstje · « **Reply #165 on:** February 27, 2011, 12:37 AM »

Welcome to DonationCoder, sujay85!

I have been told by someone (I think early on in this thread) that it already works with proxy stuff. I believe JottiQ adopts the Internet Explorer proxy information, or whatever .NET uses. If setting it there does not work, I will look into it - but again, I could swear someone already informed me JottiQ should work through proxies. I remember being relieved about it working straight away without needing to put any special effort in.

(I know very little of proxies and am not really in a position to test such stuff either; perhaps your configured proxy does not allow encrypted https 'ssl' connections?)

Ath · « **Reply #166 on:** February 27, 2011, 04:18 AM »

I could swear someone already informed me JottiQ should work through proxies.
-worstje (February 27, 2011, 12:37 AM)

That was me, when testing JottiQ on several platforms

But the devil is in the details, as usual, I have a proxy that doesn't require authentication, and sujay85 is asking for proxy with authentication... but AFAICS that's not ~~supported by~~ configurable using the standard Windows Internet settings

worstje · « **Reply #167 on:** February 27, 2011, 11:43 AM »

Dare I ask how one is supposed to browse the internet with such a proxy? If IE can't do authenticating proxies properly, you can't open any pages either right? Or am I missing something silly?

Either way, I will look into the matter when I have a bit of free time.

Ath · « **Reply #168 on:** February 27, 2011, 12:07 PM »

AFAIK, these proxies present a page when using http(s) from a browser. And most other apps should know how to pass an authenticating proxy, so it seems...

Ath · « **Reply #169 on:** February 27, 2011, 12:28 PM »

Maybe this blogpost helps? It basically means you don't have to do anything, worstje

worstje · « **Reply #170 on:** February 27, 2011, 12:32 PM »

sujay85, please give Ath's explanation a try.

I am most curious to see how that'll work out. Whether or not it works, please post your results so alternative options can be considered for implementation.

sujay85 · « **Reply #171 on:** March 04, 2011, 11:43 AM »

Hi, sorry for the late reply. Actually I haven't tried installing it there. I will try and post back... thanks...

sujay85 · « **Reply #172 on:** March 07, 2011, 12:55 AM »

I am hereby confirming that Jottiq does not work with Proxy with authentication.

Ath · « **Reply #173 on:** March 07, 2011, 01:39 AM »

Does Internet Explorer (most other browsers have other mechanisms for auth.proxies!) present you a proxy-login-page when you start browsing, or is it automagically providing the proper credentials to the proxy?

app103 · « **Reply #174 on:** March 09, 2011, 01:40 AM »

Congrats! JottiQ just got written up on MakeUseOf.

http://www.makeuseof...antivirus-apps-time/