I just made an observation. It seems that the problem occurs only if
Akregator is running.
If I don't have Akragator running, then starting multiple Qt Creator
instances work fine.
And when starting Akregator, if more than one instance of Qt Creator is
running, Akregator crashes on startup.
Weird! I narrowed it to Akregator from the QtWebEngineProcess (three
processes) it creates.
Should I file a bug against Akregator, for the crash?
On 12/15/2016 07:28 PM, Sandro Mani wrote:
On 15.12.2016 14:54, Syam Krishnan wrote:
> I am unable to start multiple Qt Creator instances on Fedora 25. If I
> start one instance, subsequent invokations seem to start the program
> but no window comes up. I can see the second instance running in
> KSysGuard, taking up 25% CPU. Even if I close the first instance, the
> second one won't come up.
> But if I then try to start it again, it comes up fine. But if I try
> to get one more instance running, that won't come up. I end up with
> one more Qt Creator process with 25% CPU utilisation.
> Anybody else seeing this?
Working fine here.
- If you run in from the terminal, do you see any abnormal output?
- Run a subsequent instance in gdb, and break when the process is
eating the cpu, then produce a backtrace via "thread apply all bt" and
post the backtrace
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org